How severe is CVE-2005-3521?

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

Is CVE-2005-3521 being actively exploited?

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

What products are affected by CVE-2005-3521?

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

How do I fix CVE-2005-3521?

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-3521 published?

CVE-2005-3521 was published on 2005-11-06 and last updated on 2026-06-16.

CVE-2005-3521

CVE-2005-3521 is a high-severity vulnerability in E107 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: 2% (73rd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: E107
Published: 2005-11-06
Last modified: 2026-06-16

Description

SQL injection vulnerability in resetcore.php in e107 0.617 through 0.6173 allows remote attackers to execute arbitrary SQL commands, bypass authentication, and inject HTML or script via the (1) a_name parameter or (2) user field of the login page.

Frequently asked questions

What is CVE-2005-3521?: SQL injection vulnerability in resetcore.php in e107 0.617 through 0.6173 allows remote attackers to execute arbitrary SQL commands, bypass authentication, and inject HTML or script via the (1) a_name parameter or (2) user field of the login page.
How severe is CVE-2005-3521?: CVE-2005-3521 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2005-3521 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (73rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-3521?: CVE-2005-3521 primarily affects E107. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2005-3521?: 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-3521 published?: CVE-2005-3521 was published on 2005-11-06 and last updated on 2026-06-16.

References

Affected products (3)

cpe:2.3:a:e107:e107:0.617:*:*:*:*:*:*:*
cpe:2.3:a:e107:e107:0.6171:*:*:*:*:*:*:*
cpe:2.3:a:e107:e107:0.6172:*:*:*:*:*:*:*

More vulnerabilities in E107

CVE-2008-1989 — Critical (CVSS 10.0): PHP remote file inclusion vulnerability in 123flashchat.php in the 123 Flash Chat 6.8.0 module for e107, when…
CVE-2022-50905 — Critical (CVSS 9.8): e107 CMS version 3.2.1 contains multiple vulnerabilities that allow cross-site scripting (XSS) attacks. The first…
CVE-2021-27885 — High (CVSS 8.8): usersettings.php in e107 through 2.3.0 lacks a certain e_TOKEN protection mechanism.
CVE-2016-10753 — High (CVSS 8.8): e107 2.1.2 allows PHP Object Injection with resultant SQL injection, because usersettings.php uses unserialize without…
CVE-2018-15901 — High (CVSS 8.8): e107 2.1.8 has CSRF in 'usersettings.php' with an impact of changing details such as passwords of users including…
CVE-2011-1513 — High (CVSS 7.5): Static code injection vulnerability in install_.php in e107 CMS 0.7.24 and probably earlier versions, when the…

All CVEs affecting E107 →