CVE-2025-15433
Received Received - Intake
Path Traversal in Shared Files WordPress Plugin Allows Sensitive File Access

Publication date: 2026-03-26

Last updated on: 2026-03-26

Assigner: WPScan

Description
The Shared Files WordPress plugin before 1.7.58 allows users with a role as low as Contributor to download any file on the web server (such as wp-config.php) via a path traversal vector
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-26
Last Modified
2026-03-26
Generated
2026-05-07
AI Q&A
2026-03-26
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
shared_files shared_files to 1.7.58 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2025-15433 is a vulnerability in the WordPress plugin "Shared Files" versions prior to 1.7.58 that allows users with Contributor-level permissions or higher to download arbitrary files from the web server by exploiting a path traversal attack.

An attacker can modify the "_sf_file_uploaded_file" parameter in a POST request to reference sensitive files outside the intended directory, such as the critical configuration file "wp-config.php".

The attack involves creating or editing a Shared File post, intercepting and altering the POST request to point to the target file, saving the post, having an administrator publish it, and then accessing the public download link to retrieve the file.

This vulnerability is classified as a path traversal (CWE-22) and has a medium severity CVSS score of 6.8.


How can this vulnerability impact me? :

This vulnerability can allow an attacker with relatively low privileges (Contributor role) to access sensitive files on the web server that should normally be protected.

Accessing files like "wp-config.php" can expose database credentials, authentication keys, and other sensitive configuration details, potentially leading to further compromise of the website or server.

Such unauthorized file access can result in data breaches, loss of confidentiality, and increased risk of website defacement or takeover.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by monitoring for suspicious POST requests to the "/wp-admin/post.php" endpoint that include the parameter "_sf_file_uploaded_file" with path traversal patterns such as "../../../" referencing sensitive files like "wp-config.php".

A possible detection method is to inspect web server logs or use network monitoring tools to filter POST requests containing the "_sf_file_uploaded_file" parameter with suspicious path traversal sequences.

Example commands to detect such attempts could include using grep on server logs:

  • grep '_sf_file_uploaded_file=.*\.\./' /var/log/apache2/access.log
  • grep '_sf_file_uploaded_file=.*wp-config.php' /var/log/apache2/access.log

Additionally, using intrusion detection systems (IDS) or web application firewalls (WAF) to alert on path traversal patterns in POST parameters can help detect exploitation attempts.


What immediate steps should I take to mitigate this vulnerability?

The immediate step to mitigate this vulnerability is to update the Shared Files WordPress plugin to version 1.7.58 or later, where the issue has been fixed.

Until the update can be applied, restrict Contributor-level users from accessing the Shared Files plugin functionality or disable the plugin entirely to prevent exploitation.

Additionally, monitor and block suspicious POST requests targeting the "_sf_file_uploaded_file" parameter with path traversal payloads using web application firewalls or other security controls.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

This vulnerability allows users with Contributor-level permissions to download arbitrary files from the web server, including sensitive configuration files such as wp-config.php. Such unauthorized access to sensitive data could lead to exposure of personal or protected information, potentially violating data protection regulations like GDPR or HIPAA.

By enabling unauthorized file access, the vulnerability increases the risk of data breaches, which may result in non-compliance with standards that require strict access controls and protection of sensitive data.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart