Is SSP Debug safe to use?

Laskyr does not give safety verdicts. SSP Debug is closed on wordpress.org. Closed on 2025-12-02 (reason given: Security Issue). Closed plugins get no updates through WordPress, so new security holes will not be fixed for you. Keep SSP Debug on the latest version and remove it if you do not use it.

Which versions of SSP Debug are vulnerable?

Known issues on record (newest first): Information disclosure (1.0.0 and older). The full list with sources is on this page.

What should I do if my SSP Debug is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update ssp-debugging). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · ssp-debugging · data as of 2026-11-04

Is SSP Debug safe? Known vulnerabilities and latest version

Status: Closed 2025-12-02
Known issues on record: 1
Unpatched in latest: 0

What to do

Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI, once you have a replacement: wp plugin deactivate ssp-debugging && wp plugin delete ssp-debugging

Check your version

Known vulnerabilities

1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 1 record(s) do not state which versions are affected.

medium 5.3 CVE-2025-13494 · published 2025-12-05

Information disclosure in SSP Debug (1.0.0 and older)

Affected: 1.0.0 and older
Fixed in: unknown
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2025-13494 Wordfence advisory Plugin source

Recent activity

2025-12-02 — closed on wordpress.org (Security Issue).
2025-12-05 — Information disclosure disclosed (CVE-2025-13494), fix version not stated.

Free. We check the CVE feeds every day and email you only when a new issue for SSP Debug (ssp-debugging) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Sensitive data exposure (1)

Where this data comes from

Version, last update, installs, closure: wordpress.org/plugins/ssp-debugging (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/ssp-debugging"><img src="https://laskyr.com/plugins/ssp-debugging/badge.svg" alt="SSP Debug vulnerability status"></a>

← Check another plugin · Free hacked-site scan