dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-28038

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Missing Authorization vulnerability in Brainstorm_Force Ultimate Addons for WPBakery Page Builder ultimate_vc_addons allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Ultimate Addons for WPBakery Page Builder: from n/a through <= 3.21.1.

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 · moderate confidence

Missing Authorization vulnerability in Brainstorm Force's Ultimate Addons for WPBakery Page Builder plugin allows authenticated attackers with low-level privileges (such as subscribers) to access functionality or data that should require higher authorization levels due to incorrectly configured access control security levels.

MitigationUpdate Ultimate Addons for WPBakery Page Builder to the latest version beyond 3.21.1 when available; until then, restrict user registration and review user role capabilities to limit low-privilege account creation.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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. Identify if Ultimate Addons for WPBakery Page Builder is installed
    Navigate to WordPress dashboard > Plugins and locate 'Ultimate Addons for WPBakery Page Builder' in the installed plugins list
    Affected if Plugin is installed and active
  2. Verify plugin version against affected range
    In Plugins list, click on the plugin to view version details, or check /wp-content/plugins/ultimate-addons-for-wpbakery-page-builder/readme.txt for version number
    Affected if Version is below the fixed release (prior to the patch addressing CVE-2026-28038)
  3. Confirm user registration configuration
    Go to WordPress Settings > General and check if 'Membership' is enabled with 'Anyone can register' selected
    Affected if User registration is open to the public and allows subscriber role creation
  4. Review subscriber-level accounts
    Navigate to WordPress Users and filter by 'Subscriber' role to identify accounts that could potentially exploit the vulnerability
    Affected if Subscriber accounts exist and the plugin exposes privileged functionality accessible to them

User is affected if the Ultimate Addons for WPBakery plugin is installed with an unpatched version and low-privilege accounts (subscribers) can be created or already exist in the WordPress environment.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Ultimate Addons for WPBakery Page Builder to the latest version beyond 3.21.1 when available; until then, restrict user registration and review user role capabilities to limit low-privilege account creation.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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