CVE-2018-16299 in the critical feed json
The Localize My Post plugin 1.0 for WordPress allows Directory Traversal via the ajax/include.php file parameter.
published 2018-09-24 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-8150
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 44.4%
- EPSS 44.4% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
The Localize My Post plugin 1.0 for WordPress allows Directory Traversal via the ajax/include.php file parameter.
Timeline
- First public exploit (EDB-45439)
- Published
Exploit prediction
44.36% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-45439 WordPress Plugin Localize My Post 1.0 - Local File Inclusion webapps, 2018-09-19
- Nuclei template WordPress Localize My Post 1.0 - Local File Inclusion nuclei detection template
- seclists.org http://seclists.org/fulldisclosure/2018/Sep/33 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com https://packetstormsecurity.com/files/149433/WordPress-Localize-My-Post-1.0-Local-File-Inclusion.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
- Technology feeds
References
-
exploit-db.com
/exploits/45439/
exploit, third-party-advisory, vdb-entry
-
seclists.org
/fulldisclosure/2018/Sep/33
mailing-list, exploit, third-party-advisory
-
packetstormsecurity.com
/files/149433/WordPress-Localize-My-Post-1.0-Local-File-Inclusion.html
exploit, third-party-advisory, vdb-entry
-
github.com
/julianburr/wp-plugin-localizemypost/issues/1
broken-link, third-party-advisory
Sources
- CVE List CVE-2018-16299
- NVD CVE-2018-16299
Fencer Vulns 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.