HomeWordPress vulnerabilitiesBranda
Branda vulnerabilities
Branda has 6 known vulnerabilities in this database. The most recent published record is dated 20 Jun 2026.
- Known vulnerabilities
- 6
- Active installs
- 20,000+
- Latest version
- 3.4.33
- Last updated
- 28 Sep 2026
- Most recent
- 20 Jun 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Privilege escalation CVE-2026-11551 | Critical 9.8 | Up to 3.4.29 | Fixed in a later version (latest 3.4.33) | 20 Jun 2026 |
| Privilege escalation CVE-2025-14998 | Critical 9.8 | Up to 3.4.24 | Fixed in a later version (latest 3.4.33) | 2 Jan 2026 |
| Cross-site scripting (XSS) CVE-2024-9371 | Medium 6.1 | Up to 3.4.19 | Fixed in a later version (latest 3.4.33) | 21 Nov 2024 |
| Cross-site scripting (XSS) CVE-2024-37239 | Medium 5.9 | Up to 3.4.18 | Fixed in a later version (latest 3.4.33) | 22 Jul 2024 |
| Sensitive data exposure CVE-2024-6554 | Medium 5.3 | Before 3.4.19 | Fixed in 3.4.19 | 11 Jul 2024 |
| Cross-site scripting (XSS) CVE-2024-5191 | Medium 6.4 | Before 3.4.18 | Fixed in 3.4.18 | 21 Jun 2024 |
Read the published descriptions
- CVE-2026-11551, 20 Jun 2026
- 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. CVE record
- CVE-2025-14998, 2 Jan 2026
- The Branda plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 3.4.24. 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. CVE record
- CVE-2024-9371, 21 Nov 2024
- The Branda - White Label & Branding, Custom Login Page Customizer plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of remove_query_arg without appropriate escaping on the URL in all versions up to, and including, 3.4.19. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. CVE record
- CVE-2024-37239, 22 Jul 2024
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WPMU DEV - Your All-in-One WordPress Platform Branda branda-white-labeling.This issue affects Branda: from n/a through <= 3.4.17. CVE record
- CVE-2024-6554, 11 Jul 2024
- The Branda - White Label WordPress, Custom Login Page Customizer plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 3.4.18. This is due the plugin utilizing composer without preventing direct access to the files. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website. CVE record
- CVE-2024-5191, 21 Jun 2024
- The Branda - White Label WordPress, Custom Login Page Customizer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘mime_types’ parameter in all versions up to, and including, 3.4.17 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
What to do if you run Branda
If you run Branda, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Branda vulnerabilities
Free. We email you when a new vulnerability is published for Branda, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.