CVE-2026-32395
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 · uneditedMissing Authorization vulnerability in Xpro Xpro Addons For Beaver Builder – Lite xpro-addons-beaver-builder-elementor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Xpro Addons For Beaver Builder – Lite: from n/a through <= 1.5.6.
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 confidenceMissing Authorization vulnerability in Xpro Addons For Beaver Builder – Lite allows attackers to exploit incorrectly configured access control security levels. This broken access control issue enables unauthenticated or unauthorized users to access functionality they should not have permission to use.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installation and activation statusNavigate to WordPress admin > Plugins and confirm Xpro Addons For Beaver Builder - Lite is installed and active, or check the filesystem at wp-content/plugins/ for the plugin directoryAffected if The plugin is installed and active in WordPress
-
Determine installed plugin versionCheck the plugin's main PHP file header for the 'Version' field, or view the plugin in WordPress admin plugins list which displays the version numberAffected if The installed version matches or precedes any version with known patches (compare against published advisory versions)
-
Inspect admin interface access controlsAttempt to access plugin-specific admin pages or functionality while logged out or as a low-privilege user (subscriber level), observing whether authorization checks are properly enforcedAffected if Unauthenticated users or unauthorized roles can access plugin admin functions or settings they should not reach
-
Review plugin capability checksExamine the plugin's PHP files for missing current_user_can() or capability verification checks before sensitive operations, particularly in AJAX handlers and admin action hooksAffected if Critical functions lack proper capability verification or authorization gates
-
Test cross-privilege access scenariosCreate test users with different roles (subscriber, contributor, author, editor) and attempt to access plugin features designated for administrators onlyAffected if Lower-privileged users can perform actions restricted to administrators
A user is affected if Xpro Addons For Beaver Builder - Lite is active and lacks proper authorization enforcement, allowing unauthorized access to protected functionality.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to a patched version of Xpro Addons For Beaver Builder – Lite when available. Until then, restrict access to the plugin's admin interfaces and verify proper authorization checks are enforced at all user privilege levels.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32395 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32395 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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