How severe is CVE-2005-3969?

CVE-2005-3969 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2005-3969 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (65th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2005-3969?

CVE-2005-3969 primarily affects Mxchange. In total, 8 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2005-3969?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2005-3969 published?

CVE-2005-3969 was published on 2005-12-03 and last updated on 2026-06-16.

CVE-2005-3969

CVE-2005-3969 is a high-severity vulnerability in Mxchange with a CVSS 2.0 base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 1% (65th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Mxchange
Published: 2005-12-03
Last modified: 2026-06-16

Description

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

Frequently asked questions

What is CVE-2005-3969?: SQL injection vulnerability in MXChange before 0.2.0-pre10 PL492 allows remote attackers to execute arbitrary SQL commands via unknown vectors.
How severe is CVE-2005-3969?: CVE-2005-3969 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2005-3969 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (65th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-3969?: CVE-2005-3969 primarily affects Mxchange. In total, 8 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2005-3969?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2005-3969 published?: CVE-2005-3969 was published on 2005-12-03 and last updated on 2026-06-16.

References

Affected products (8)

cpe:2.3:a:mxchange:mxchange:0.2.0_pre3:*:*:*:*:*:*:*
cpe:2.3:a:mxchange:mxchange:0.2.0_pre4:*:*:*:*:*:*:*
cpe:2.3:a:mxchange:mxchange:0.2.0_pre5:*:*:*:*:*:*:*
cpe:2.3:a:mxchange:mxchange:0.2.0_pre6:*:*:*:*:*:*:*
cpe:2.3:a:mxchange:mxchange:0.2.0_pre7:*:*:*:*:*:*:*
cpe:2.3:a:mxchange:mxchange:0.2.0_pre8:*:*:*:*:*:*:*
cpe:2.3:a:mxchange:mxchange:0.2.0_pre9:*:*:*:*:*:*:*
cpe:2.3:a:mxchange:mxchange:0.2.0_pre10:*:*:*:*:*:*:*

More vulnerabilities in Mxchange

CVE-2005-3970 — Medium (CVSS 4.3): Cross-site scripting (XSS) vulnerability in MXChange before 0.2.0-pre10 PL492 allows remote attackers to inject…

All CVEs affecting Mxchange →