dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-2030

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The WPBakery Page Builder Addons by Livemesh plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `[lvca_carousel]` and `[lvca_posts_carousel]` shortcode attributes in all versions up to, and including, 3.9.4 due to insufficient input sanitization and output escaping. Specifically, shortcode attributes are encoded with `wp_json_encode()` and output into single-quoted `data-settings` HTML attributes without using `esc_attr()`, allowing attackers to break out of the attribute by injecting single quotes. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 confidence

The WPBakery Page Builder Addons plugin for WordPress contains a stored XSS vulnerability in versions up to 3.9.4. The plugin uses `wp_json_encode()` to encode shortcode attributes for `[lvca_carousel]` and `[lvca_posts_carousel]` but outputs them into single-quoted `data-settings` HTML attributes without applying `esc_attr()`. This allows authenticated attackers with Contributor-level access to inject single quotes and break out of the attribute context to execute arbitrary JavaScript.

MitigationUpdate the Livemesh WPBakery Addons plugin to version 3.9.5 or later which should implement proper output escaping using `esc_attr()` for all shortcode attributes before rendering into HTML contexts.

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Livemesh WPBakery Addons and note the version number displayed, or inspect the plugin header in wp-content/plugins/livemesh-wpbakery-addons/livemesh-wpbakery-addons.php for 'Version: x.x.x'
    Affected if Version is 3.9.4 or lower (any version below 3.9.5)
  2. Verify shortcode presence
    Search the WordPress database or site content for '[lvca_carousel]' or '[lvca_posts_carousel]' shortcode usage in posts, pages, or widgets
    Affected if Either shortcode is present in any published content
  3. Confirm user role access
    Navigate to Users > All Users in WordPress admin and review role assignments; check if any users have Contributor role or higher
    Affected if At least one user has Contributor role or higher, allowing authenticated exploitation
  4. Inspect data-settings attribute output
    View the HTML source of a page containing the vulnerable shortcode and locate the data-settings attribute in the carousel container div; verify if the attribute value contains unescaped quotes or suspicious script content
    Affected if The data-settings attribute contains raw single quotes or appears to break out of the attribute context

You are affected if the Livemesh WPBakery Addons plugin version is 3.9.4 or lower AND either the lvca_carousel or lvca_posts_carousel shortcode is in use on your site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Livemesh WPBakery Addons plugin to version 3.9.5 or later which should implement proper output escaping using `esc_attr()` for all shortcode attributes before rendering into HTML contexts.

Recommended fix Moderate confidence

Version 3.9.5 or later

  1. 1. Update the WPBakery Page Builder Addons by Livemesh plugin to version 3.9.5 or later.
  2. 2. Navigate to Dashboard > Plugins in WordPress admin.
  3. 3. Locate the 'WPBakery Page Builder Addons by Livemesh' plugin.
  4. 4. Click 'Update now' if an update is available, or manually upload version 3.9.5 or higher if automatic updates are not enabled.
  5. 5. After updating, verify that carousel shortcodes ([lvca_carousel] and [lvca_posts_carousel]) function correctly on the site.
  6. 6. Clear any caching plugins or server-side caches to ensure the updated code is served.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2030 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2030 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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