Ultimate Addons For Wpbakery Page BuilderWordPress extension · Brainstormforce
CVE-2023-51402
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Brain Storm Force Ultimate Addons for WPBakery Page Builder.This issue affects Ultimate Addons for WPBakery Page Builder: from n/a through 3.19.17.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Ultimate Addons for WPBakery Page Builder WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions by forcing their browsers to send malicious requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Ultimate Addons For Wpbakery Page BuilderWordPress extension
<= 3.19.17CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin is installedLog in to WordPress admin, go to Plugins > Installed Plugins, and look for 'Ultimate Addons for WPBakery Page Builder' or 'Ultimate Addons For WPBakery' in the list. Note whether it is active or not.Affected if The plugin is installed and active.
-
Identify installed versionIn the WordPress admin Plugins page, click on the plugin name to view details, or check the main plugin file (typically /wp-content/plugins/ultimate-addons-for-wpbakery/main.php or similar) for the 'Version' header in the plugin comments.Affected if The installed version is 3.19.17 or lower.
-
Verify nonce protection is missingIf you have file access, inspect the plugin PHP files, particularly AJAX handlers and admin action handlers. Search for the absence of wp_nonce_field, wp_nonce_url, or check_admin_referer calls before state-changing operations like settings saves, post updates, or plugin config changes.Affected if State-changing admin actions in the plugin lack nonce verification.
A user is affected if the Ultimate Addons for WPBakery Page Builder plugin is active with version 3.19.17 or lower and lacks proper nonce validation on sensitive admin actions.
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 dataThe plugin vendor should implement anti-CSRF tokens (nonces) for all state-changing operations, particularly admin actions and AJAX endpoints, and verify the nonce on the server side before processing any request.
Fix this in Ultimate Addons For Wpbakery Page Builder
Scoped from the published advisory
- Consultation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51402 — 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-2023-51402 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