CVE-2013-1470 json
Cross-site scripting (XSS) vulnerability in calendar/index.php in the Calendar plugin in Geeklog before 1.8.2sr1 and 2.0.0 before 2.0.0rc2…
published 12y ago modified 4mo ago also EUVD-2013-1506
- 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 79%
- public exploits
- 0
- none known
Summary
Cross-site scripting (XSS) vulnerability in calendar/index.php in the Calendar plugin in Geeklog before 1.8.2sr1 and 2.0.0 before 2.0.0rc2 allows remote attackers to inject arbitrary web script or HTML via the calendar_type parameter to submit.php.
Patch / fix
Is CVE-2013-1470 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 FencerExploit prediction
1.89% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- archives.neohapsis.com http://archives.neohapsis.com/archives/bugtraq/2013-02/0154.html referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/120593/Geeklog-1.8.2-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified
- htbridge.com https://www.htbridge.com/advisory/HTB23143 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
-
geeklog.net
/article.php/geeklog-1.8.2sr1
patch, vendor-advisory
-
archives.neohapsis.com
/archives/bugtraq/2013-02/0154.html
mailing-list, exploit
-
packetstormsecurity.com
/files/120593/Geeklog-1.8.2-Cross-Site-Scripting.html
exploit
-
htbridge.com
/advisory/HTB23143
exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/82326
vdb-entry
Sources
- CVE List CVE-2013-1470
- NVD CVE-2013-1470
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.