# CVE-2025-13494: SSP Debug <= 1.0.0 - Unauthenticated Sensitive Information Exposure

> Unauthenticated attackers can access sensitive debug logs containing user data and internal paths due to missing access controls on log files.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-jhqp-8v5c-95qc

## What is CVE-2025-13494?

CVE-2025-13494 is a medium-severity vulnerability in jimmyredline80 SSP Debug, published on 5 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-13494?


## How do I fix CVE-2025-13494?

No fix has been published for CVE-2025-13494 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-13494 being exploited?

There is no known exploitation of CVE-2025-13494 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13494 and fix it if it is affected.

What it is: CVE-2025-13494 is a medium-severity vulnerability in jimmyredline80 SSP Debug, published on 5 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13494 in the wild and no public exploit code.

Affected product: jimmyredline80 SSP Debug. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-13494/ (Markdown: https://insights.sbomify.com/CVE-2025-13494/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-13494
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-13494
- OSV: https://osv.dev/vulnerability/CVE-2025-13494

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-13494/
Summaries are generated and may contain mistakes; the official description above is the record.