CVE-2010-2917 json
Multiple cross-site scripting (XSS) vulnerabilities in index.php in AJ Square AJ Article 3.0 allow remote attackers to inject arbitrary web…
published 16y ago modified 4mo ago also EUVD-2010-2921
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 1
- Exploit-DB
Summary
Multiple cross-site scripting (XSS) vulnerabilities in index.php in AJ Square AJ Article 3.0 allow remote attackers to inject arbitrary web script or HTML via the (1) emailid, (2) fname, (3) lname, (4) company, (5) address1, (6) address2, (7) city, (8) state, (9) zipcode, (10) phone, and (11) fax parameters in an update action. NOTE: some of these details are obtained from third party information.
Is CVE-2010-2917 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-14354)
- Published
Exploit prediction
1.72% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-14354 AJ Article 3.0 - Cross-Site Scripting webapps, 2010-07-13
- packetstormsecurity.org http://packetstormsecurity.org/1007-exploits/ajarticle-xss.txt 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
-
exploit-db.com
/exploits/14354
exploit
-
packetstormsecurity.org
/1007-exploits/ajarticle-xss.txt
exploit
-
secunia.com
/advisories/40560
third-party-advisory, vendor-advisory
-
osvdb.org
/66279
vdb-entry
-
securityfocus.com
/bid/41576
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/60357
vdb-entry
Sources
- CVE List CVE-2010-2917
- NVD CVE-2010-2917
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.