Approved changes feed: RSS · Atom
cpe:2.3:a:jimmyredline80:ssp_debug:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Jimmyredline80 (3e53b99c-2bc3-58f7-b413-c5f5a53054f2) |
|---|---|
| Product | Ssp Debug (559d6e37-59d9-5ba3-8e7e-71d767bd562e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-13494 |
vulnerable | 2026-06-08 07:04:32.414747 |
SSP Debug <= 1.0.0 - Unauthenticated Sensitive Information Exposure
MEDIUM (5.3)
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: 2025-12-05T04:29:11.275Z
Updated: 2026-04-08T16:58:06.482Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.