CVE-2024-31933
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 Live Composer Team Page Builder: Live Composer.This issue affects Page Builder: Live Composer: from n/a through 1.5.35.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Page Builder: Live Composer WordPress plugin. Attackers can craft malicious requests that trick authenticated administrators into performing unintended actions (e.g., modifying page content, changing settings) without their consent.
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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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 Live Composer plugin is installedNavigate to WordPress Admin > Plugins and confirm 'Page Builder: Live Composer' is installed and activeAffected if The plugin is installed and active in WordPress
-
Identify installed plugin versionIn Plugins list, click on the plugin name to view version details, or inspect the plugin header in /wp-content/plugins/live-composer/includes/framework.phpAffected if Version is within the affected range (prior to patch)
-
Check AJAX handlers for nonce verificationSearch plugin files (especially /js/ and /includes/ directories) for AJAX action handlers; inspect whether each handler calls wp_verify_nonce() or check_ajax_referer() before processingAffected if AJAX actions process requests without verifying nonce tokens
-
Inspect form submissions for nonce validationReview plugin PHP files for form output (e.g., settings pages, content save forms); verify each form includes a nonce field and the handler validates it via wp_verify_nonce()Affected if Forms submit without nonce fields or handlers skip validation
-
Review admin action hooks for CSRF protectionExamine admin_init, admin_post and similar hooks that handle state-changing operations; check if they validate nonces before executing changesAffected if Admin actions execute without nonce verification
If the Live Composer plugin is active and its state-changing operations (AJAX, forms, admin actions) lack proper nonce verification, the installation is vulnerable to CVE-2024-31933.
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 dataImplement WordPress nonces (anti-CSRF tokens) on all state-changing operations (forms and AJAX actions) and verify the nonce on the server side before processing any request.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31933 — 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-2024-31933 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