dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-3897

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 Livemesh Addons for Beaver Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `labb_admin_ajax` AJAX action in all versions up to, and including, 3.9.2 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 confidence

The Livemesh Addons for Beaver Builder plugin for WordPress has a Stored XSS vulnerability in the `labb_admin_ajax` AJAX action. The AJAX handler verifies a nonce but fails to check user capabilities, allowing authenticated attackers with Subscriber-level access to modify plugin settings and inject malicious scripts that execute when administrators view settings or users visit the frontend.

MitigationAdd a capability check (e.g., `manage_options`) to the AJAX handler to ensure only administrators can modify settings, and implement proper input sanitization and output escaping for all settings values before storing and displaying them.

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 if Livemesh Addons for Beaver Builder plugin is installed
    Navigate to WordPress Admin > Plugins and look for 'Livemesh Addons for Beaver Builder' in the installed plugins list
    Affected if The plugin is installed and active in WordPress
  2. Determine the installed plugin version
    In WordPress Admin > Plugins, click on the plugin name to view the version details, or open the main plugin PHP file and look for a version constant or header
    Affected if The version is any version prior to when the capability check was implemented (compare your version against any official patch release)
  3. Verify if the labb_admin_ajax action lacks capability checks
    Locate the AJAX handler for labb_admin_ajax in the plugin files and examine whether it calls current_user_can() with a privileged capability such as manage_options before processing settings changes
    Affected if The AJAX handler processes requests without verifying the user has elevated privileges
  4. Confirm low-privilege user access to the AJAX endpoint
    Test the AJAX endpoint wp_ajax_labb_admin_ajax using a Subscriber-level account, or review the capability check logic in the handler code to verify it permits subscriber-level access
    Affected if The AJAX action accepts and processes requests from authenticated users with Subscriber role
  5. Inspect plugin settings for injected scripts
    View the Livemesh plugin settings pages in the WordPress admin, or examine the wp_options table for livemesh-related entries, looking for unsanitized script tags or event handlers in stored values
    Affected if Plugin settings contain unsanitized HTML or JavaScript that would execute when displayed to administrators or frontend users

Your environment is affected if the Livemesh Addons for Beaver Builder plugin is installed and the labb_admin_ajax AJAX action is accessible to users with Subscriber-level permissions without proper capability validation.

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

Add a capability check (e.g., `manage_options`) to the AJAX handler to ensure only administrators can modify settings, and implement proper input sanitization and output escaping for all settings values before storing and displaying them.

Recommended fix High confidence

Version 3.9.3 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Livemesh Addons for Beaver Builder' in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Alternatively, download the latest version from wordpress.org/plugins/livemesh-addons-for-beaver-builder/ and upload it via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version is 3.9.3 or later under Plugins > Installed Plugins
  7. Clear any caching plugins if enabled, then test the frontend and admin settings page to confirm functionality

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3897 — 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-3897 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