dbcve.org
CWE-640Weakness · CWE-640

CVE-2026-11551

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Branda WordPress plugin versions up to 3.4.29 lacks proper identity validation when processing password change requests, allowing unauthenticated attackers to reset arbitrary user passwords including administrator accounts and gain full site access.

MitigationImmediately update Branda plugin to version 3.4.30 or later; review and reset passwords for all administrator accounts and audit user accounts for unauthorized changes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Branda plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Branda - White Label Branding for WordPress'. Note the version number displayed under the plugin name.
    Affected if The installed version is 3.4.29 or earlier (any version up to and including 3.4.29).
  2. Confirm plugin is active
    In the same Plugins page, verify that Branda plugin shows as 'Active' rather than 'Inactive' or 'Must Use'.
    Affected if The plugin is active and the version from step 1 is 3.4.29 or earlier.
  3. Review administrator account audit logs
    Check WordPress user logs or security logs for any recent password changes on administrator-level accounts, especially if performed by unknown users or from unexpected IP addresses. Access this via WordPress activity logs plugin if installed, or server access logs.
    Affected if Any administrator password resets occurred that were not initiated by legitimate administrators.
  4. Inspect user table for unauthorized changes
    Access the WordPress database (via phpMyAdmin or wp-cli) and query the wp_users and wp_usermeta tables. Look for recent changes to user_pass (password hash) or user_login fields, particularly for users with wp_capabilities containing 'administrator'.
    Affected if Password hash or user_login fields for administrator accounts were modified recently without legitimate admin action.

You are affected if the Branda plugin version is 3.4.29 or earlier and the plugin is active, or if unauthorized administrator password changes are detected in logs or the user database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately update Branda plugin to version 3.4.30 or later; review and reset passwords for all administrator accounts and audit user accounts for unauthorized changes.

Recommended fix Moderate confidence

Latest version of Branda plugin (greater than 3.4.29)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Branda plugin
  4. Check if the current version is 3.4.29 or below
  5. If vulnerable, click 'Update Now' to install the latest version
  6. If no update is available, manually download the latest version from wordpress.org and reinstall
  7. Verify the updated version number after upgrading
  8. Ensure the admin account password is changed as a precaution

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11551 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11551 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data