CVE-2026-1557 json
WP Responsive Images <= 1.0 - Unauthenticated Path Traversal to Arbitrary File Read via src
published 2026-02-26 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-8805
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
The WP Responsive Images plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.0 via the 'src' parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information.
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 8 mo ago
Exploit prediction
1.87% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template WP Responsive Images <= 1.0 - Arbitrary File Read nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- stuartbates WP Responsive Images
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/22c6f81b-d456-44b9-ba6c-8b207a9ee6e1?source=cve
- plugins.trac.wordpress.org /browser/wp-responsive-images/trunk/SBOutputFile.php#L33
- plugins.trac.wordpress.org /browser/wp-responsive-images/trunk/image_handler.php#L28
- plugins.trac.wordpress.org /browser/wp-responsive-images/tags/1.0/image_handler.php#L28
- plugins.trac.wordpress.org /browser/wp-responsive-images/trunk/WPResponsiveImages.php#L265
- plugins.trac.wordpress.org /browser/wp-responsive-images/tags/1.0/WPResponsiveImages.php#L265
- plugins.trac.wordpress.org /browser/wp-responsive-images/tags/1.0/SBOutputFile.php#L33
Sources
- CVE List CVE-2026-1557
- NVD CVE-2026-1557
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.