CVE-2010-4821 json
Cross-site scripting (XSS) vulnerability in phpMyFAQ before 2.6.9 allows remote attackers to inject arbitrary web script or HTML via the PA…
published 14y ago modified 4mo ago also EUVD-2010-4786
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.7%
- EPSS 4.7% chance of exploitation in 30 days, percentile 91%
- public exploits
- 1
- Exploit-DB
Summary
Cross-site scripting (XSS) vulnerability in phpMyFAQ before 2.6.9 allows remote attackers to inject arbitrary web script or HTML via the PATH_INFO to index.php.
Is CVE-2010-4821 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-34785)
- Published
Exploit prediction
4.74% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-34785 PHPMyFAQ 2.6.x - 'index.php' Cross-Site Scripting webapps, 2010-09-28
- dl.packetstormsecurity.net http://dl.packetstormsecurity.net/1009-exploits/phpmyfaq268-xss.txt referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/bugtraq/2010/Sep/207 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
dl.packetstormsecurity.net
/1009-exploits/phpmyfaq268-xss.txt
exploit
-
seclists.org
/bugtraq/2010/Sep/207
mailing-list, exploit
-
secunia.com
/advisories/41625
third-party-advisory, vendor-advisory
-
phpmyfaq.de
/advisory_2010-09-28.php
vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/62092
vdb-entry
-
openwall.com
/lists/oss-security/2012/03/08/2
mailing-list
-
openwall.com
/lists/oss-security/2012/03/08/7
mailing-list
-
osvdb.org
/68268
vdb-entry
Sources
- CVE List CVE-2010-4821
- NVD CVE-2010-4821
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.