CVE-2015-4614 json
Multiple SQL injection vulnerabilities in includes/Function.php in the Easy2Map plugin before 1.2.5 for WordPress allow remote attackers to…
published 11y ago modified 4mo ago also EUVD-2015-4634
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.2%
- EPSS 5.2% chance of exploitation in 30 days, percentile 92%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in includes/Function.php in the Easy2Map plugin before 1.2.5 for WordPress allow remote attackers to execute arbitrary SQL commands via the mapName parameter in an e2m_img_save_map_name action to wp-admin/admin-ajax.php and other unspecified vectors.
Patch / fix
Is CVE-2015-4614 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-37534)
- Published
Exploit prediction
5.21% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-37534 WordPress Plugin Easy2Map 1.24 - SQL Injection webapps, 2015-07-08
- vapid.dhs.org http://www.vapid.dhs.org/advisory.php?v=131 referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/fulldisclosure/2015/Jul/18 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
-
wordpress.org
/plugins/easy2map/changelog/
patch
-
exploit-db.com
/exploits/37534/
exploit
-
vapid.dhs.org
/advisory.php?v=131
exploit
-
seclists.org
/fulldisclosure/2015/Jul/18
mailing-list, exploit
- plugins.trac.wordpress.org /changeset/1191455/easy2map
-
securityfocus.com
/archive/1/535922/100/0/threaded
mailing-list
Sources
- CVE List CVE-2015-4614
- NVD CVE-2015-4614
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.