dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-1557

HIGH · 7.5 CVSS v3.1 Published 2026-02-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WP Responsive Images WordPress plugin versions up to and including 1.0 contains a path traversal vulnerability via the 'src' parameter, allowing unauthenticated attackers to read arbitrary files on the server. The lack of input sanitization on the src parameter enables attackers to use '..' sequences to traverse the file system and access sensitive files such as wp-config.php.

MitigationUpdate the plugin to a patched version immediately. If no patched version is available, deactivate the plugin. As a defense-in-depth measure, ensure WordPress file permissions restrict read access to sensitive files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the WP Responsive Images plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WP Responsive Images' or check the plugin directory /wp-content/plugins/ for a folder named 'wp-responsive-images' or similar
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Check the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find WP Responsive Images and view the version number displayed below the plugin name; alternatively, read the main plugin PHP file header for the Version field
    Affected if The version is 1.0 or lower (any version up to and including 1.0 is affected)
  3. Determine if the plugin is active
    In WordPress admin > Plugins > Installed Plugins, check if WP Responsive Images shows as 'Active' under the plugin status
    Affected if The plugin is currently activated and accessible to unauthenticated users
  4. Identify the vulnerable endpoint and parameter
    Examine HTTP requests to the plugin's AJAX handler or direct PHP file that processes the 'src' parameter; common paths include /wp-admin/admin-ajax.php or a direct file in the plugin folder; use browser dev tools or a proxy to inspect network traffic when the plugin functionality is triggered
    Affected if The plugin processes a 'src' parameter without sanitization and the endpoint is accessible to unauthenticated users
  5. Test for the path traversal vulnerability (safe read test)
    Send a crafted GET request to the vulnerable endpoint with src=../../../../wp-config.php (or ../../../../../../wp-config.php depending on depth) and check if the file content is returned in the response; use curl: curl 'http://target/wp-admin/admin-ajax.php?action=responsive_img&src=../../wp-config.php'
    Affected if The response contains the contents of wp-config.php or other sensitive files, confirming the path traversal is exploitable

A user is affected if the WP Responsive Images plugin (version 1.0 or lower) is installed and active, exposing an unauthenticated endpoint that accepts a 'src' parameter without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a patched version immediately. If no patched version is available, deactivate the plugin. As a defense-in-depth measure, ensure WordPress file permissions restrict read access to sensitive files.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1557 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1557 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data