CVE-2015-6969 json
Cross-site scripting (XSS) vulnerability in js/2k11.min.js in the 2k11 theme in Serendipity before 2.0.2 allows remote attackers to inject…
published 2015-09-16 11 y ago modified 2026-06-17 4 mo ago also EUVD-2015-6901
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
Cross-site scripting (XSS) vulnerability in js/2k11.min.js in the 2k11 theme in Serendipity before 2.0.2 allows remote attackers to inject arbitrary web script or HTML via a user name in a comment, which is not properly handled in a Reply link.
Patch / fix
Exploit prediction
1.94% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- seclists.org http://seclists.org/fulldisclosure/2015/Sep/9 referenced PoC, tagged "exploit" by a source, unverified
- blog.curesec.com http://blog.curesec.com/article/blog/Serendipity-201-Persistent-XSS-51.html referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/133427/Serendipity-2.0.1-Cross-Site-Scripting.html 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
-
seclists.org
/fulldisclosure/2015/Sep/9
mailing-list, exploit, patch
-
blog.s9y.org
/archives/265-Serendipity-2.0.2-Security-Fix-Release.html
patch, vendor-advisory
-
blog.curesec.com
/article/blog/Serendipity-201-Persistent-XSS-51.html
exploit
-
packetstormsecurity.com
/files/133427/Serendipity-2.0.1-Cross-Site-Scripting.html
exploit
Sources
- CVE List CVE-2015-6969
- NVD CVE-2015-6969
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.