Page BuilderWordPress extension · Wpbakery
CVE-2023-31213
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 · uneditedAuth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in WPBakery Page Builder plugin <= 6.13.0 versions.
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 confidenceStored XSS vulnerability in WPBakery Page Builder allows authenticated users with contributor-level access or higher to inject malicious JavaScript that persists on the server and executes when other users view the affected content.
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
Page BuilderWordPress extension
< 6.13.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Identify WPBakery Page Builder installationCheck for the plugin in WordPress by reviewing the plugin files at /wp-content/plugins/js_composer/ or by checking the WordPress plugins admin panelAffected if The plugin is present in the WordPress installation
-
Determine installed versionLocate the main plugin file (typically js_composer/include/classes/core/class-vc-manage.php or similar) and read the version constant, or check the plugin header in the main PHP fileAffected if The version number found is less than 6.13.0
-
Verify contributor-level user access existsReview WordPress user roles in the admin panel under Users > All Users, or query the wp_options table for user_role assignments to confirm contributor, author, editor, or administrator accounts existAffected if At least one user account with contributor-level or higher access exists in the system
-
Check for custom content elementsInspect the database for any custom vc_element shortcodes in wp_posts content that may contain unsanitized user input, or examine recent posts/pages created with the WPBakery editorAffected if Content created with WPBakery's front-end editor contains raw or improperly escaped user-supplied data in custom element attributes
The environment is affected if WPBakery Page Builder is installed with a version below 6.13.0 and contributor-level or higher user accounts have created content using the visual editor that could contain unsanitized input.
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.
dbcve · scoped6.13.0
Update WPBakery Page Builder to a version newer than 6.13.0, or apply input sanitization and output encoding to all user-supplied content rendered by the plugin.
6.13.0 or later
- Update WPBakery Page Builder plugin to version 6.13.0 or later through WordPress admin > Plugins > Updates, or upload the latest version from wordpress.org
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Page Builder
Scoped from the published advisory
- 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-2023-31213 — 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-31213 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