CVE-2005-3969: SQL injection vulnerability in MXChange before 0.2.0-pre10 PL492 allows remote attackers to execute arbitrary

This month

HIGH 7.5DOWNGRADE

CVE-2005-3969 is a high-severity flaw (CVSS 7.5) affecting mxchange. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

SQL injection vulnerability in MXChange before 0.2.0-pre10 PL492 allows remote attackers to execute arbitrary SQL commands via unknown vectors.

Why this priority

High severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	1.2% (top 32%)
CISA exploited list	No
Published	2005-12-03
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: mxchange

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2005-12-03 19:03 UTCPublished CVE record published
2026-06-16 22:17 UTCUpdated Record last modified

mxchange mxchange DOWNGRADE

Affected: 0.2.0_pre3 · 0.2.0_pre4 · 0.2.0_pre5 · 0.2.0_pre6 · 0.2.0_pre7 · 0.2.0_pre8 · 0.2.0_pre9 · 0.2.0_pre10

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.2.0_pre3

1. Check installed version

apt-cache policy mxchange || rpm -q mxchange || mxchange --version

2. No fixed release: DOWNGRADE to a release before 0.2.0_pre3 (Debian / Ubuntu)

apt-cache madison mxchange sudo apt install mxchange=<VERSION_BEFORE_0.2.0_pre3> sudo apt-mark hold mxchange

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list mxchange sudo dnf downgrade mxchange-<VERSION_BEFORE_0.2.0_pre3> sudo dnf versionlock add mxchange

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2005-3969?

mxchange: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-3969 being exploited?

CVE-2005-3969 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2005-3969 affect?

CVE-2005-3969 affects mxchange. Severity is high (CVSS 7.5). SQL injection vulnerability in MXChange before 0.2.0-pre10 PL492 allows remote attackers to execute arbitrary SQL commands via unknown vectors.

How urgent is CVE-2005-3969?

Priority 43/100. High severity

Related CVEs

CVE-2005-3970 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in MXChange before 0.2.0-pre10 PL492 allows remote attackers to injec

References

← Back to latest CVEs