CVE-2025-13494
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-05

Last updated on: 2025-12-08

Assigner: Wordfence

Description
The SSP Debug plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.0.0. This is due to the plugin storing PHP error logs in a predictable, web-accessible location (wp-content/uploads/ssp-debug/ssp-debug.log) without any access controls. This makes it possible for unauthenticated attackers to view sensitive debugging information including full URLs, client IP addresses, User-Agent strings, WordPress user IDs, and internal filesystem paths.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-05
Last Modified
2025-12-08
Generated
2026-06-16
AI Q&A
2025-12-05
EPSS Evaluated
2026-06-14
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wordfence ssp_debug 1.0.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions
Instant insights powered by AI
Executive Summary

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.

Impact Analysis

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.

Detection Guidance

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.

Mitigation Strategies

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.

Compliance Impact

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]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-13494. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart