CVE-2025-13494: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in jimmyredline80 SSP Debug
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.
AI Analysis
Technical Summary
CVE-2025-13494 is a vulnerability in the jimmyredline80 SSP Debug WordPress plugin (versions up to 1.0.0) where PHP error logs are stored in a predictable, web-accessible directory (wp-content/uploads/ssp-debug/ssp-debug.log) without any access restrictions. This misconfiguration allows unauthenticated attackers to retrieve sensitive debugging information including full URLs, client IP addresses, User-Agent strings, WordPress user IDs, and internal filesystem paths. The issue is categorized under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) and has a CVSS 3.1 base score of 5.3 (medium severity). No patch or official fix has been documented in the provided information.
Potential Impact
An attacker can access sensitive debugging information without authentication, potentially aiding further attacks or reconnaissance. The exposed data includes full URLs, client IP addresses, User-Agent strings, WordPress user IDs, and internal filesystem paths. There is no indication of impact on integrity or availability. No known exploits are reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should restrict access to the wp-content/uploads/ssp-debug/ssp-debug.log file by implementing web server access controls (e.g., .htaccess rules) to prevent unauthorized access to the debug log. Disabling the SSP Debug plugin if not needed can also reduce exposure.
CVE-2025-13494: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in jimmyredline80 SSP Debug
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-13494 is a vulnerability in the jimmyredline80 SSP Debug WordPress plugin (versions up to 1.0.0) where PHP error logs are stored in a predictable, web-accessible directory (wp-content/uploads/ssp-debug/ssp-debug.log) without any access restrictions. This misconfiguration allows unauthenticated attackers to retrieve sensitive debugging information including full URLs, client IP addresses, User-Agent strings, WordPress user IDs, and internal filesystem paths. The issue is categorized under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) and has a CVSS 3.1 base score of 5.3 (medium severity). No patch or official fix has been documented in the provided information.
Potential Impact
An attacker can access sensitive debugging information without authentication, potentially aiding further attacks or reconnaissance. The exposed data includes full URLs, client IP addresses, User-Agent strings, WordPress user IDs, and internal filesystem paths. There is no indication of impact on integrity or availability. No known exploits are reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should restrict access to the wp-content/uploads/ssp-debug/ssp-debug.log file by implementing web server access controls (e.g., .htaccess rules) to prevent unauthorized access to the debug log. Disabling the SSP Debug plugin if not needed can also reduce exposure.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-11-20T21:57:46.360Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69326360f88dbe026c71795d
Added to database: 12/5/2025, 4:45:20 AM
Last enriched: 4/9/2026, 4:30:48 PM
Last updated: 5/9/2026, 10:01:06 PM
Views: 199
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.