Summaryinfo

A vulnerability categorized as critical has been discovered in jhimross Debugger & Troubleshooter Plugin up to 1.3.2 on WordPress. The impacted element is the function wp_debug_troubleshoot_simulate_user. The manipulation of the argument cookie results in cookie validation. This vulnerability is identified as CVE-2026-5130. The attack can be executed remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in jhimross Debugger & Troubleshooter Plugin up to 1.3.2 on WordPress. Affected is the function wp_debug_troubleshoot_simulate_user. The manipulation of the argument cookie with an unknown input leads to a cookie validation vulnerability. CWE is classifying the issue as CWE-565. The product relies on the existence or values of cookies when performing security-critical operations, but it does not properly ensure that the setting is valid for the associated user. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The weakness was released by Nabil Irawan. The advisory is available at wordfence.com. This vulnerability is traded as CVE-2026-5130 since 03/30/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. Technical details are known, but there is no available exploit.

Upgrading to version 1.3.2 eliminates this vulnerability.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

• WordPress Plugin

Vendor

• jhimross

Name

• Debugger & Troubleshooter Plugin

Version

• 1.3.0
• 1.3.1
• 1.3.2

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion