CVE-2025-13494
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe SSP Debug WordPress plugin (versions up to 1.0.0) stores PHP error logs in a predictable, web-accessible path (wp-content/uploads/ssp-debug/ssp-debug.log) without any access restrictions. Unauthenticated attackers can directly request this file via a web browser to obtain sensitive debugging data including client IP addresses, User-Agent strings, WordPress user IDs, full URLs, and internal filesystem paths.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if SSP Debug plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'SSP Debug' in the list, or inspect the filesystem at wp-content/plugins/ for a folder named 'ssp-debug'Affected if The plugin folder 'ssp-debug' exists in wp-content/plugins/ or the plugin appears in WordPress admin
-
Verify the plugin versionCheck the main plugin file (e.g., ssp-debug.php) for the version comment or check the WordPress plugin repository metadataAffected if The installed version is 1.0.0 or any earlier version (up to and including 1.0.0)
-
Check if the debug log file existsLook for the file at wp-content/uploads/ssp-debug/ssp-debug.log via FTP, SSH, or the hosting file managerAffected if The file ssp-debug.log exists in the wp-content/uploads/ssp-debug/ directory
-
Verify web accessibility of the log fileAttempt to access the log file via a web browser at http(s)://yourdomain.com/wp-content/uploads/ssp-debug/ssp-debug.log - if the file downloads or displays content, it is web-accessibleAffected if The log file can be retrieved over HTTP without authentication or access restrictions
-
Inspect log file contents for sensitive dataIf the log file exists, open it and check for sensitive information such as IP addresses, User-Agent strings, WordPress user IDs, URLs, or filesystem pathsAffected if The log file contains any sensitive debugging information including client IPs, user IDs, or internal paths
You are affected if the SSP Debug plugin (version 1.0.0 or earlier) is installed and the ssp-debug.log file exists and is accessible via web request.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataMove the log file outside the webroot directory or restrict access via .htaccess rules (deny from all) in the ssp-debug folder; alternatively, disable debug logging entirely in production WordPress environments.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13494 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13494 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data