Home

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.

PUBLISHED Reserved 2025-11-20 | Published 2025-12-05 | Updated 2025-12-05 | Assigner Wordfence




MEDIUM: 5.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Problem types

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

Product status

Default status
unaffected

* (semver)
affected

Timeline

2025-12-04:Disclosed

Credits

Itthidej Aramsri finder

References

www.wordfence.com/...-1522-43cd-af78-9b734c66af8c?source=cve

plugins.trac.wordpress.org/...-debugging/trunk/ssp-debug.php

plugins.trac.wordpress.org/...gging/tags/1.0.0/ssp-debug.php

cve.org (CVE-2025-13494)

nvd.nist.gov (CVE-2025-13494)