Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
UnratedPublic exploit

Branda WordPress Plugin Unauthenticated Account Takeover Privilege Escalation

IdentifiersCVE-2026-11551CWE-639

CVE-2026-11551 affects the Branda plugin for WordPress in all versions up to and including 3.4.29. The vulnerability is caused by improper validation of a user's identity before allowing a password update. As a result, an unauthenticated attacker can change the password of an arbitrary user account without proving control of that account. Because this can be performed against administrator accounts, the issue results in account takeover and subsequent privilege escalation within the affected WordPress site.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthenticated attacker to reset passwords for arbitrary users, including administrators. This enables full takeover of targeted WordPress accounts and privilege escalation to the level of the compromised account. If an administrator account is targeted, the attacker can gain administrative access to the WordPress instance and perform any actions available to that role.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, disable the Branda plugin until an updated version can be deployed. As a compensating control, monitor for unexpected password changes, newly established administrator sessions, and other signs of account takeover, and reset credentials for potentially affected accounts. Restricting access to WordPress administrative interfaces does not fully address the underlying flaw if the vulnerable password-update functionality remains reachable.

Remediation

Patch, then assume compromise.

Update the Branda plugin to a version newer than 3.4.29 once the vendor-provided fix is available. If a patched release has already been published by the vendor, upgrade immediately to that fixed version across all affected WordPress installations.
PUBLIC EXPLOITS

Exploits

2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).

VALID 2 / 3 TOTALView more in app
CVE-2026-11551-PoCMaturityPoCVerified exploit

This repository is a small standalone PHP proof-of-concept plus a README for CVE-2026-11551 affecting the Branda/White Label & Branding WordPress plugin on multisite deployments. The code is not a remote exploit script by itself; instead, it is intended to run within a WordPress environment and demonstrates vulnerable application logic involving wp_update_user(), wp_insert_user(), and Branda's wp_pre_insert_user_data filter. Repository structure is minimal: one executable PHP PoC file and one documentation file. The PHP file defines and immediately invokes poc_privilege_escalation(). That function inserts a crafted pending signup row into the WordPress signups table with serialized metadata containing a known password, then simulates an admin editing an existing user by changing user_login to match the pending signup. According to the README and PoC logic, Branda's signup-password filter reads the pending signup metadata during user update and hashes the supplied password again, even though WordPress core has already hashed the password earlier in the update flow. The PoC then attempts authentication and expects failure, using that failure to confirm the double-hash condition. Main exploit capability: forced password corruption/account lockout of an existing user, including an administrator, by causing the plugin to overwrite the account password with a double-hashed value when the username matches a pending signup. The README frames this as privilege escalation/account takeover, but the actual PoC most clearly demonstrates denial of access and unsafe password reassignment behavior. It does not include a customizable shell payload, command execution, or network callback. Fingerprintable targets and artifacts are primarily WordPress-specific: the wp_signups and wp_users tables, the /wp-admin/user-edit.php administrative path described in the attack flow, and external reference URLs to the vulnerable plugin source and Wordfence advisory. Overall maturity is best classified as POC: it demonstrates the vulnerable condition and impact but is not weaponized or automated for broad exploitation.

ubaydevDisclosed Jun 21, 2026phpmarkdownweblocal
2026-11551MaturityPoCVerified exploit

Repository contains a single Python exploit script and a minimal README. The main file, cve_2026_11551.py, is an operational exploit for CVE-2026-11551 affecting the WordPress Branda White Label & Branding plugin <= 3.4.29. The script targets a logic flaw in Branda’s signup password handling where password_1 can overwrite the password of an existing user because the hook runs on all wp_insert_user/wp_update_user calls without properly excluding updates. The exploit supports two paths: single-site WordPress registration through /wp-login.php?action=register and multisite signup/activation through /wp-signup.php followed by /wp-activate.php. It performs reconnaissance to identify plugin presence/version, determine whether the site is multisite, check whether registration is open, and assess whether Branda password fields are present. It generates attacker-controlled passwords and unique email addresses, attempts takeover against supplied or default usernames, supports optional proxying and SSL verification disablement, and can run against a single target or mass-scan a list with threading. Successful takeovers are written to branda_results.txt along with metadata and cookies. Overall, this is a real exploit rather than a detector, and its purpose is unauthenticated privilege escalation via account takeover of existing WordPress users.

xxconiDisclosed Jun 19, 2026pythonmarkdownwebnetwork
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
WpmudevBrandaapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity10

Community discussion across Reddit, Mastodon, and other social sources.