CVE-2025-13494
BaseFortify
Publication date: 2025-12-05
Last updated on: 2025-12-08
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordfence | ssp_debug | 1.0.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-200 | The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the SSP Debug plugin for WordPress (versions up to and including 1.0.0). The plugin stores PHP error logs in a predictable and publicly accessible location without any access controls. As a result, unauthenticated attackers can access these logs and view sensitive debugging information such as full URLs, client IP addresses, User-Agent strings, WordPress user IDs, and internal filesystem paths.
How can this vulnerability impact me? :
The vulnerability can lead to sensitive information exposure, allowing attackers to gather detailed information about the website and its users. This information could be used to facilitate further attacks, compromise user privacy, or exploit other vulnerabilities within the system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by checking if the file wp-content/uploads/ssp-debug/ssp-debug.log exists and is accessible via the web. For example, use commands like 'curl -I http://yourwordpresssite.com/wp-content/uploads/ssp-debug/ssp-debug.log' to see if the log file is publicly accessible. Additionally, scanning your web server for the presence of this file or searching your filesystem for ssp-debug.log can help identify exposure.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the wp-content/uploads/ssp-debug/ssp-debug.log file by implementing proper access controls, such as using .htaccess rules or web server configuration to deny public access. Alternatively, remove or disable the SSP Debug plugin if it is not needed, or update it if a fixed version becomes available.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability exposes sensitive debugging information such as full URLs, client IP addresses, User-Agent strings, WordPress user IDs, and internal filesystem paths to unauthenticated attackers due to the plugin storing PHP error logs in a predictable, web-accessible location without access controls. Such exposure of personal and system information can lead to non-compliance with data protection regulations like GDPR and HIPAA, which require protection of personal data and sensitive information from unauthorized access. [2, 3]