Branda – White Label & Branding, Free Login Page Customizer <= 3.4.29 - Unauthenticated Privilege Escalation via Account Takeover
Strategic Overview
- Status
- Patched in 3.4.31
- Affected Plugin
- Branda – White Label & Branding, Free Login Page Customizer
- Affected Version
<= 3.4.29- CVSS
- 9.8Critical
- Weakness type
- CWE-640 · Weak Password Recovery Mechanism for Forgotten Password
- CVE
CVE-2026-11551
At a glance
CVE-2026-11551 is a critical-severity Weak Password Recovery Mechanism for Forgotten Password vulnerability in the Branda WordPress plugin, affecting versions <= 3.4.29. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.4.31; sites on affected versions should update now. Disclosed June 2026, reported by thevietronin.
Vulnerability Overview
The Branda plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 3.4.29. This is due to the plugin not properly validating a user's identity prior to updating their password. This makes it possible for unauthenticated attackers to change arbitrary user's passwords, including administrators, and leverage that to gain access to their account.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-640: Weak Password Recovery Mechanism for Forgotten Password
Reaching this weakness in Branda <= 3.4.29 takes no account at all. A weak password recovery mechanism means the path that lets someone back into an account without their password is easier to complete than the password itself.
An attacker takes over an account through the recovery flow without ever seeing the password, and on an administrator account that is full control of the site. For Branda the fix is 3.4.31: builds <= 3.4.29 are affected, anything from 3.4.31 onward is not.
Remediation
Update to version 3.4.31, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Branda 3.4.31 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Branda – White Label & Branding, Free Login Page Customizer
- 9.8CVE-2025-14998: Branda Privilege Escalation
CVE-2025-14998 - 6.4CVE-2024-5191: Branda Stored XSS
CVE-2024-5191 - 6.1CVE-2024-9371: Branda Reflected XSS
CVE-2024-9371 - 5.3CVE-2024-6554: Branda Full Path Disclosure
CVE-2024-6554 - 5.3CVE-2023-51542: Branda <= 3.4.14 IP Address Spoofing
CVE-2023-51542 - 4.4CVE-2024-37239: Branda <= 3.4.17 Stored Cross-Site Scripting
CVE-2024-37239 - 4.4Branda – White Label WordPress <= 3.4.8.1 Stored Cross-Site Scripting
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C