# CVE-2026-5130: Debugger & Troubleshooter <= 1.3.2 - Unauthenticated Privilege Escalation to Administrator via Cookie Manipulation

> Unauthenticated attackers can gain administrator access by manipulating a cookie, allowing full site control and privilege escalation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Mar 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-24w3-v7fc-cjwv

## What is CVE-2026-5130?

CVE-2026-5130 is a high-severity authentication bypass vulnerability in jhimross Debugger & Troubleshooter, published on 30 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Debugger & Troubleshooter plugin for WordPress was vulnerable to Unauthenticated Privilege Escalation in versions up to and including 1.3.2. This was due to the plugin accepting the wp_debug_troubleshoot_simulate_user cookie value directly as a user ID without any cryptographic validation or authorization checks. The cookie value was used to override the determine_current_user filter, which allowed unauthenticated attackers to impersonate any user by simply setting the cookie to their target user ID. This made it possible for unauthenticated attackers to gain administrator-level access and perform any privileged actions including creating new administrator accounts, modifying site content, installing plugins, or taking complete control of the WordPress site. The vulnerability was fixed in version 1.4.0 by implementing a cryptographic token-based validation system where only administrators can initiate user simulation, and the cookie contains a random 64-character token that must be validated against database-stored mappings rather than accepting arbitrary user IDs.

Weakness: CWE-565 (Reliance on Cookies without Validation and Integrity Checking)

## Which versions are affected by CVE-2026-5130?


## How do I fix CVE-2026-5130?

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

## Is CVE-2026-5130 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5130 and fix it if it is affected.

What it is: CVE-2026-5130 is a high-severity authentication bypass vulnerability in jhimross Debugger & Troubleshooter, published on 30 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5130 in the wild and no public exploit code.

Affected product: jhimross Debugger & Troubleshooter. 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-2026-5130/ (Markdown: https://insights.sbomify.com/CVE-2026-5130/index.md)
```

## Sources

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

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