Skip to content
Fencer Intel
high 7.5

CVE-2019-14205 in the critical feed json

A Local File Inclusion vulnerability in the Nevma Adaptive Images plugin before 0.6.67 for WordPress allows remote attackers to retrieve ar…

published 7y ago modified 4mo ago also EUVD-2019-5455

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
63.4%
EPSS 63.4% chance of exploitation in 30 days, percentile 99.2%
public exploits
0
none known, plus a Nuclei check

Summary

A Local File Inclusion vulnerability in the Nevma Adaptive Images plugin before 0.6.67 for WordPress allows remote attackers to retrieve arbitrary files via the $REQUEST['adaptive-images-settings']['source_file'] parameter in adaptive-images-script.php.

Patch / fix

  • nevma adaptive_images 0.6.67

Is CVE-2019-14205 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 Fencer

Exploit prediction

63.38% chance of exploitation in the next 30 days, higher than 99.2% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Nuclei template WordPress Nevma Adaptive Images <0.6.67 - Local File Inclusion nuclei detection template
  • markgruffer.github.io https://markgruffer.github.io/2019/07/19/adaptive-images-for-wordpress-0-6-66-lfi-rce-file-deletion.html referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/markgruffer/markgruffer.github.io/blob/master/_posts/2019-07-19-adaptive-images-for-wordpress-0-6-66-lfi-rce-file-deletion.markdown referenced PoC, tagged "exploit" by a source, unverified
  • wpvulndb.com https://wpvulndb.com/vulnerabilities/9468 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/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

Sources

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.