# CVE-2026-1557: WP Responsive Images <= 1.0 - Unauthenticated Path Traversal to Arbitrary File Read via src

> Unauthenticated attackers can read arbitrary files on the server via path traversal in the WP Responsive Images plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-hvcw-qp77-8m24

## What is CVE-2026-1557?

CVE-2026-1557 is a high-severity path traversal vulnerability in stuartbates WP Responsive Images, published on 26 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-1557?


## How do I fix CVE-2026-1557?

No fix has been published for CVE-2026-1557 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1557 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1557 exists.

Public exploit code:

- WP Responsive Images <= 1.0 - Arbitrary File Read (nuclei): http/cves/2026/CVE-2026-1557.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1557 and fix it if it is affected.

What it is: CVE-2026-1557 is a high-severity path traversal vulnerability in stuartbates WP Responsive Images, published on 26 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1557 exists.

Affected product: stuartbates WP Responsive Images. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1557/ (Markdown: https://insights.sbomify.com/CVE-2026-1557/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1557
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1557
- OSV: https://osv.dev/vulnerability/CVE-2026-1557

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1557/
Summaries are generated and may contain mistakes; the official description above is the record.