CVE-2025-13972
Arbitrary File Read in WatchTowerHQ WordPress Plugin Allows Data Exposure
Publication date: 2025-12-12
Last updated on: 2026-04-08
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpress | wordpress | * |
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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows authenticated administrators to read arbitrary files on the server, potentially exposing sensitive information such as database credentials and authentication keys. Such exposure could lead to unauthorized access to personal or protected data, thereby risking non-compliance with standards and regulations like GDPR and HIPAA that require protection of sensitive information.
Can you explain this vulnerability to me?
This vulnerability exists in the WatchTowerHQ plugin for WordPress (up to version 3.15.0) and allows an authenticated attacker with administrator-level access and a valid access token to read arbitrary files on the server. It occurs due to insufficient path validation in the handle_big_object_download_request function via the 'wht_download_big_object_origin' parameter.
How can this vulnerability impact me? :
An attacker exploiting this vulnerability can read arbitrary files on the server, potentially accessing sensitive information such as database credentials and authentication keys. This can lead to unauthorized access to critical data and compromise the security of the WordPress site.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring requests to the Watchtower plugin's download endpoints, especially those containing the parameter 'wht_download_big_object_origin'. Look for authenticated requests (with valid access tokens) attempting to access files outside the intended backup directory via path traversal patterns (e.g., '../'). Commands to detect such activity could include web server log searches like: 1. Using grep to find suspicious requests in access logs: grep 'wht_download_big_object_origin' /var/log/apache2/access.log | grep '\.\./' 2. Using curl to test the endpoint (requires valid access token): curl -i 'https://yourwordpresssite.com/wht_download_big_object/{access_token}/../../../../etc/passwd/0/100' 3. Using network monitoring tools to filter HTTP requests containing 'wht_download_big_object_origin' parameter. These methods help identify attempts to exploit the path traversal vulnerability by checking for unusual file path patterns in requests. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1. Restrict access to the Watchtower plugin's download endpoints to trusted administrators only, ensuring access tokens are kept secure and rotated if compromised. 2. Disable or remove the Watchtower plugin until a patched version (beyond 3.15.0) is available that properly validates file paths to prevent path traversal. 3. Monitor and block suspicious requests attempting to exploit the 'wht_download_big_object_origin' parameter. 4. Apply any available security patches or updates from the plugin maintainers addressing this vulnerability. 5. Review server file permissions to limit exposure of sensitive files in case of exploitation. [1, 3]