CVE-2014-4718 json
Multiple cross-site request forgery (CSRF) vulnerabilities in Lunar CMS before 3.3-3 allow remote attackers to hijack the authentication of…
published 2014-07-03 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-4637
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 1
- Exploit-DB
Summary
Multiple cross-site request forgery (CSRF) vulnerabilities in Lunar CMS before 3.3-3 allow remote attackers to hijack the authentication of administrators for requests that (1) add Super users via a request to admin/user_create.php or conduct cross-site scripting (XSS) attacks via the (2) email or (3) subject parameter in contact_form.ext.php to admin/extensions.php.
Patch / fix
- lunarcms.com/Get.html patch
Timeline
- First public exploit (EDB-33830)
- Published
Exploit prediction
2.31% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-33830 Lunar CMS 3.3 - Cross-Site Request Forgery / Persistent Cross-Site Scripting webapps, 2014-06-21
- packetstormsecurity.com http://packetstormsecurity.com/files/127188/Lunar-CMS-3.3-CSRF-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
lunarcms.com
/Get.html
patch
-
exploit-db.com
/exploits/33830
exploit
-
packetstormsecurity.com
/files/127188/Lunar-CMS-3.3-CSRF-Cross-Site-Scripting.html
exploit
-
securityfocus.com
/bid/68153
vdb-entry
-
osvdb.org
/show/osvdb/108351
vdb-entry
-
secunia.com
/advisories/59411
third-party-advisory
- zeroscience.mk /en/vulnerabilities/ZSL-2014-5188.php
-
osvdb.org
/show/osvdb/108350
vdb-entry
Sources
- CVE List CVE-2014-4718
- NVD CVE-2014-4718
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.