CVE-2026-3895
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 · uneditedThe WPBakery Page Builder Addons by Livemesh plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `lvca_admin_ajax` AJAX action in all versions up to, and including, 3.9.4 due to missing authorization checks and insufficient input sanitization. The AJAX handler verifies a nonce but does not check user capabilities. This makes it possible for authenticated attackers with Subscriber-level access and above to modify plugin settings and inject malicious scripts that execute when administrators access the plugin settings page or when any user visits the frontend.
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 confidenceThe WPBakery Page Builder Addons by Livemesh plugin for WordPress has a stored XSS vulnerability in the lvca_admin_ajax AJAX handler. Although the handler verifies a CSRF nonce, it fails to check user capabilities, allowing any authenticated user with Subscriber-level access or higher to modify plugin settings. Combined with insufficient input sanitization, attackers can inject malicious JavaScript that executes when administrators view the settings page or when frontend users visit the site.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify the Livemesh WPBakery plugin is installedNavigate to WordPress admin dashboard > Plugins and look for 'WPBakery Page Builder Addons by Livemesh' or 'Livemesh Addons for WPBakery Page Builder' in the installed plugins listAffected if The plugin appears in the plugins list and is activated
-
Locate the lvca_admin_ajax handler fileCheck the plugin directory (typically wp-content/plugins/livemesh-wpbakery-addons/) for AJAX handler files, specifically looking for files containing 'lvca_admin_ajax' or the admin AJAX endpoint registrationAffected if The plugin contains an AJAX handler registered with action name 'lvca_admin_ajax'
-
Inspect capability checks in the AJAX handlerExamine the PHP file registering the lvca_admin_ajax action - look for current_user_capability checks (e.g., 'manage_options') before processing settings modifications; absence of such checks indicates the vulnerabilityAffected if The AJAX handler lacks capability verification (e.g., no current_user_can('manage_options') check) before processing settings
-
Check input sanitization on settings fieldsReview the PHP code that processes and saves settings via lvca_admin_ajax - inspect whether functions like sanitize_text_field, esc_attr, or wp_kses are applied to user inputs before storageAffected if Settings inputs are stored without proper sanitization functions, allowing script injection
-
Verify authenticated user accessConfirm that WordPress user roles with Subscriber-level access exist on the site; the vulnerability allows any authenticated user (Subscriber role or higher) to modify plugin settingsAffected if The site has user accounts with Subscriber, Contributor, Author, or Editor roles who can access wp-admin/AJAX endpoints
Your environment is affected if the Livemesh WPBakery plugin is installed with the lvca_admin_ajax handler that lacks capability checks and proper input sanitization, allowing any authenticated user to inject malicious scripts into plugin settings.
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 · scopedAdd proper WordPress capability checks (e.g., manage_options) to the lvca_admin_ajax action and implement robust input sanitization for all settings fields before storage and output.
Latest version of WPBakery Page Builder Addons by Livemesh (version higher than 3.9.4)
- 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
- 2. Locate the 'WPBakery Page Builder Addons by Livemesh' plugin
- 3. Check the current installed version of the plugin
- 4. If the installed version is 3.9.4 or lower, update the plugin to the latest available version
- 5. After updating, verify the update was successful by checking the plugin version
- 6. Confirm that the lvca_admin_ajax action now properly checks user capabilities before executing
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3895 — 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-3895 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