CVE-2015-2678 json
Multiple cross-site scripting (XSS) vulnerabilities in MetalGenix GeniXCMS before 0.0.2 allow remote attackers to inject arbitrary web scri…
published 11y ago modified 4mo ago also EUVD-2015-2769
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.4%
- EPSS 5.4% chance of exploitation in 30 days, percentile 92%
- public exploits
- 1
- Exploit-DB
Summary
Multiple cross-site scripting (XSS) vulnerabilities in MetalGenix GeniXCMS before 0.0.2 allow remote attackers to inject arbitrary web script or HTML via the (1) cat parameter in the categories page to gxadmin/index.php or (2) page parameter to index.php.
Patch / fix
Is CVE-2015-2678 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-36321)
- Published
Exploit prediction
5.36% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-36321 GeniXCMS 0.0.1 - Multiple Vulnerabilities webapps, 2015-03-10
- packetstormsecurity.com http://packetstormsecurity.com/files/130771/GeniXCMS-0.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
- github.com /semplon/GeniXCMS/commit/698245488343396185b1b49e7482ee5b25541815
-
blog.metalgenix.com
/genixcms-v0-0-2-release-security-and-bug-fixes/17
patch
-
exploit-db.com
/exploits/36321
exploit
-
packetstormsecurity.com
/files/130771/GeniXCMS-0.0.1-Cross-Site-Scripting.html
exploit
- zeroscience.mk /en/vulnerabilities/ZSL-2015-5233.php
-
securityfocus.com
/bid/73301
vdb-entry
- github.com /semplon/GeniXCMS/issues/7
-
osvdb.org
/show/osvdb/119394
vdb-entry
Sources
- CVE List CVE-2015-2678
- NVD CVE-2015-2678
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.