CVE-2010-1186 json
Cross-site scripting (XSS) vulnerability in xml/media-rss.php in the NextGEN Gallery plugin before 1.5.2 for WordPress allows remote attack…
published 16y ago modified 4mo ago also EUVD-2010-1216
- 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 xml/media-rss.php in the NextGEN Gallery plugin before 1.5.2 for WordPress allows remote attackers to inject arbitrary web script or HTML via the mode parameter.
Patch / fix
Is CVE-2010-1186 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-12098)
- Published
Exploit prediction
4.73% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-12098 WordPress Plugin NextGEN Gallery 1.5.1 - Cross-Site Scripting webapps, 2010-04-06
- securityfocus.com http://www.securityfocus.com/bid/39250 referenced PoC, tagged "exploit" by a source, unverified
- coresecurity.com http://www.coresecurity.com/content/nextgen-gallery-xss-vulnerability 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
-
wordpress.org
/extend/plugins/nextgen-gallery/changelog/
patch
-
exploit-db.com
/exploits/12098
exploit
-
securityfocus.com
/bid/39250
vdb-entry, exploit
-
coresecurity.com
/content/nextgen-gallery-xss-vulnerability
exploit
-
secunia.com
/advisories/39341
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/57562
vdb-entry
-
vupen.com
/english/advisories/2010/0821
vdb-entry
Sources
- CVE List CVE-2010-1186
- NVD CVE-2010-1186
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.