CVE-2012-6493 json
Cross-site request forgery (CSRF) vulnerability in Rapid7 Nexpose Security Console before 5.5.4 allows remote attackers to hijack the authe…
published 2014-02-04 12 y ago modified 2026-06-16 4 mo ago also EUVD-2012-6346
- 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
Cross-site request forgery (CSRF) vulnerability in Rapid7 Nexpose Security Console before 5.5.4 allows remote attackers to hijack the authentication of unspecified victims for requests that delete scan data and sites via a request to data/site/delete.
Patch / fix
Timeline
- First public exploit (EDB-23924)
- 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-23924 Nexpose Security Console - Cross-Site Request Forgery webapps, 2013-01-06
- archives.neohapsis.com http://archives.neohapsis.com/archives/bugtraq/2013-01/0014.html referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/119260/Nexpose-Security-Console-Cross-Site-Request-Forgery.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
-
community.rapid7.com
/docs/DOC-2155#release1
patch, vendor-advisory
-
exploit-db.com
/exploits/23924
exploit
-
archives.neohapsis.com
/archives/bugtraq/2013-01/0014.html
mailing-list, exploit
-
packetstormsecurity.com
/files/119260/Nexpose-Security-Console-Cross-Site-Request-Forgery.html
exploit
-
osvdb.org
/88923
vdb-entry
Sources
- CVE List CVE-2012-6493
- NVD CVE-2012-6493
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.