What the vulnerability does
01Description
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.
Explanation of Vulnerability in Simple Terms
02Summary
SSP Debug versions 1.0.0 and earlier expose sensitive information over the network without requiring authentication or user interaction. An attacker can read this exposed data directly. The vulnerability affects the debug functionality and has a network attack surface with low complexity.
What an attacker can do
03Attacker Capabilities
Read sensitive information exposed by the debug component without authentication.
Potential impact on your site
04Site Impact
Sensitive data may be exposed to unauthenticated attackers if SSP Debug is installed and enabled.
Conditions required to exploit
05Prerequisites
Network access to the affected system; no authentication or user interaction required.
Key dates
06Disclosure timeline
December 5, 2025
CVE published
April 8, 2026
Record updated