CVE-2026-57754
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 · uneditedContributor Cross Site Scripting (XSS) in Livemesh Addons for WPBakery Page Builder <= 3.9.4 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 · moderate confidenceA Cross-Site Scripting (XSS) vulnerability in Livemesh Addons for WPBakery Page Builder allows attackers with Contributor-level WordPress privileges to inject malicious scripts. The vulnerability exists in versions 3.9.4 and below. XSS occurs when user-supplied input is rendered without proper sanitization or output encoding.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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.
-
Identify if Livemesh Addons for WPBakery is installedCheck your WordPress plugins directory or navigate to Plugins > Installed Plugins in the WordPress admin dashboard. Look for 'Livemesh Addons for WPBakery Page Builder' in the list of active plugins.Affected if The plugin is not found in the installed plugins list, then this CVE does not apply.
-
Determine the installed version of the pluginIn the WordPress admin, go to Plugins > Installed Plugins and find the Livemesh Addons for WPBakery Page Builder entry. The version number is displayed below the plugin name. Alternatively, inspect the main plugin file (usually named 'livemesh-wpbakery-addons.php') and look for the 'Version' header in the plugin comment block.Affected if The version is 3.9.4 or below, indicating the plugin is within the affected version range.
-
Verify user role permissions for the pluginNavigate to WordPress Users > All Users and review the roles assigned to site users. Identify whether any users have the Contributor role, as this is the privilege level required to exploit the XSS vulnerability.Affected if Contributor-level or higher untrusted users exist with access to create or edit content using the plugin's elements.
-
Inspect plugin settings for user input fieldsAccess the plugin settings via the WordPress admin menu (usually under 'Livemesh Addons' or within the WPBakery Page Builder element settings). Look for any fields that accept user-supplied text input, such as custom heading text, button labels, or content module fields.Affected if The plugin contains user input fields that could accept malicious script payloads without visible sanitization indicators.
You are affected if Livemesh Addons for WPBakery Page Builder is installed with version 3.9.4 or below AND Contributor-level users can access the plugin's content creation features.
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 Livemesh Addons for WPBakery Page Builder to a version newer than 3.9.4. If immediate update is not possible, implement input validation and output escaping on all user-generated content fields within the plugin.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57754 — 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-57754 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