dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-14998

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-02
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.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.

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 fails to validate user identity before processing password update requests, allowing unauthenticated attackers to reset any user's password (including administrators) by supplying the target username and a new password. This enables complete account takeover and privilege escalation to admin level.

MitigationUpdate Branda plugin to version 3.4.25 or later which contains proper identity validation before password changes. If update is not possible immediately, consider disabling the plugin or implementing web application firewall rules to block password reset endpoints.

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 is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Branda' (also known as 'Branda - White Labeling'), or check the filesystem at /wp-content/plugins/ for a folder containing 'branda' or 'white-label-cms'.
    Affected if Branda plugin is installed and active on the WordPress site
  2. Check installed Branda version
    In WordPress admin, go to Plugins > Installed Plugins > Branda, or read the version from the plugin's main PHP file header (typically /wp-content/plugins/white-label-cms/white-label-cms.php or similar). Compare the version number to 3.4.25.
    Affected if The installed version is lower than 3.4.25 (for example, 3.4.24, 3.4.20, etc.)
  3. Confirm password reset feature is enabled
    In WordPress admin, go to Branda settings > Security or Password settings panel. Look for any password reset, password change, or account recovery functionality that Branda may have added or modified. Check if these features are toggled to 'enabled' or 'active'.
    Affected if Password reset or password change features provided by Branda are enabled on the site
  4. Verify WordPress password reset endpoint is accessible
    Visit the WordPress password reset endpoint (typically /wp-login.php?action=lostpassword or /wp-admin/?action=lostpassword) and inspect whether the Branda plugin's custom password reset handler is processing requests instead of the default WordPress handler.
    Affected if Branda's custom password reset functionality is intercepting requests at the default WordPress password reset URLs

A site is affected if the Branda plugin is installed with a version lower than 3.4.25 and the plugin's password reset features are enabled, allowing unauthenticated attackers to reset any user's password.

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

Update Branda plugin to version 3.4.25 or later which contains proper identity validation before password changes. If update is not possible immediately, consider disabling the plugin or implementing web application firewall rules to block password reset endpoints.

Recommended fix Moderate confidence

Branda version 3.4.25

  1. 1. Update the Branda plugin to version 3.4.25 or later through the WordPress admin dashboard under Plugins > All Plugins > Branda > Update Now
  2. 2. After updating, verify that the plugin is running version 3.4.25 or higher by checking Plugins > Installed Plugins > Branda
  3. 3. As a precaution, review user accounts to ensure no unauthorized password changes have occurred
  4. 4. Consider resetting passwords for administrative accounts as a security best practice

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14998 — 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-2025-14998 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