CVE-2026-1557
BaseFortify
Publication date: 2026-02-26
Last updated on: 2026-02-27
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "CVE-2026-1557 is a Path Traversal vulnerability in the WP Responsive Images plugin for WordPress, affecting all versions up to and including 1.0. The vulnerability arises from improper validation of the 'src' parameter used to specify image file paths."}, {'type': 'paragraph', 'content': "Specifically, the plugin's image handler script takes the 'src' parameter from an HTTP GET request and concatenates it directly with the server's document root to form a file path without sufficient sanitization. This allows unauthenticated attackers to manipulate the 'src' parameter to traverse directories and read arbitrary files on the server."}, {'type': 'paragraph', 'content': 'As a result, attackers can access sensitive files outside the intended image directories, potentially exposing confidential information.'}] [4, 1]
How can this vulnerability impact me? :
This vulnerability allows unauthenticated attackers to read arbitrary files on the server hosting the WordPress site using the vulnerable plugin.
- Exposure of sensitive information stored in files outside the web root or image directories.
- Potential leakage of configuration files, credentials, or other confidential data.
- Increased risk of further attacks due to information disclosure.
The vulnerability has a CVSS v3.1 base score of 7.5, indicating a high severity with network attack vector, low attack complexity, no privileges required, and no user interaction needed.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "This vulnerability can be detected by monitoring HTTP requests to the WordPress site that include the 'src' parameter in the URL, especially those attempting directory traversal patterns such as '../' sequences."}, {'type': 'paragraph', 'content': 'A practical approach is to look for suspicious GET requests targeting the image handler script or URLs rewritten by the plugin that contain path traversal attempts.'}, {'type': 'list_item', 'content': "Use web server access logs to search for requests with 'src' parameters containing '../' or other traversal patterns."}, {'type': 'list_item', 'content': 'Example command to detect such attempts in Apache logs: grep -E "src=.*\\.\\./" /var/log/apache2/access.log'}, {'type': 'list_item', 'content': "Alternatively, use network monitoring tools or intrusion detection systems to alert on HTTP requests with suspicious 'src' parameter values."}] [4]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'Immediate mitigation steps include disabling or uninstalling the vulnerable WP Responsive Images plugin until a patched version is available.'}, {'type': 'paragraph', 'content': "Additionally, restrict access to the image handler script or the plugin's directories via web server configuration to prevent unauthorized access."}, {'type': 'list_item', 'content': "Apply input validation and sanitization on the 'src' parameter to prevent directory traversal, if you have the capability to patch the plugin code."}, {'type': 'list_item', 'content': 'Monitor and block suspicious requests attempting to exploit the vulnerability using web application firewalls or security plugins.'}, {'type': 'list_item', 'content': 'Keep the WordPress installation and all plugins updated to the latest versions once a fix is released.'}] [4]