wpmudev Branda Plugin up to 3.4.29 on WordPress password recovery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 4.97 |
Summary
A vulnerability has been found in wpmudev Branda Plugin up to 3.4.29 on WordPress and classified as critical. This affects an unknown function. Performing a manipulation results in password recovery. This vulnerability is identified as CVE-2026-11551. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.
Details
A vulnerability classified as critical has been found in wpmudev Branda Plugin up to 3.4.29 on WordPress. This affects an unknown part. The manipulation with an unknown input leads to a password recovery vulnerability. CWE is classifying the issue as CWE-640. The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was released by Tran Van Nhan and Vo Van Minh. The advisory is shared at wordfence.com. This vulnerability is uniquely identified as CVE-2026-11551 since 06/08/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.
Upgrading to version 3.4.29 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-38097). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 3.4.0
- 3.4.1
- 3.4.2
- 3.4.3
- 3.4.4
- 3.4.5
- 3.4.6
- 3.4.7
- 3.4.8
- 3.4.9
- 3.4.10
- 3.4.11
- 3.4.12
- 3.4.13
- 3.4.14
- 3.4.15
- 3.4.16
- 3.4.17
- 3.4.18
- 3.4.19
- 3.4.20
- 3.4.21
- 3.4.22
- 3.4.23
- 3.4.24
- 3.4.25
- 3.4.26
- 3.4.27
- 3.4.28
- 3.4.29
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 9.8
CNA Vector (Wordfence): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Password recoveryCWE: CWE-640
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Branda Plugin 3.4.29
Timeline
06/08/2026 CVE reserved06/20/2026 Advisory disclosed
06/20/2026 VulDB entry created
06/20/2026 VulDB entry last update
Sources
Advisory: wordfence.comResearcher: Tran Van Nhan, Vo Van Minh
Status: Confirmed
CVE: CVE-2026-11551 (🔒)
GCVE (CVE): GCVE-0-2026-11551
GCVE (VulDB): GCVE-100-372501
EUVD: 🔒
Entry
Created: 06/20/2026 09:37Updated: 06/20/2026 12:26
Changes: 06/20/2026 09:37 (65), 06/20/2026 12:26 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.