dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-3896

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 SiteOrigin Widgets plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `lsow_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 SiteOrigin Widgets WordPress plugin suffers from a stored XSS vulnerability in the lsow_admin_ajax AJAX handler. Although the handler verifies a nonce token, it fails to perform capability/authorization checks, allowing any authenticated user with Subscriber-level access or higher to inject malicious JavaScript via plugin settings that executes on the frontend and in the admin settings page.

MitigationUpdate to the latest version of the plugin (beyond 3.9.2) which should include proper capability verification and input sanitization. Until then, restrict subscriber-level account creation and monitor for suspicious admin_ajax calls.

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. Verify Livemesh SiteOrigin Widgets plugin is installed
    In WordPress admin, go to Plugins > Instored Plugins and look for 'Livemesh SiteOrigin Widgets' or check the plugin files in wp-content/plugins/ for the lsow folder. Open the main plugin file to read the Version header.
    Affected if The plugin is installed and active
  2. Determine installed plugin version
    Open the main plugin PHP file (usually lsow-plugin.php or similar in wp-content/plugins/lsow/) and locate the 'Version' defined in the plugin header comment. Compare this version to the fixed version 3.9.2.
    Affected if Version is 3.9.2 or lower, or version cannot be determined and the plugin is present
  3. Check for subscriber-level user accounts
    In WordPress admin, go to Users > All Users and review the Role column. Look for any accounts assigned the 'Subscriber' role or any role ranked Subscriber or higher (Contributor, Author, Editor, Admin).
    Affected if There exists at least one user account with Subscriber-level access or higher who is not fully trusted
  4. Inspect plugin settings for suspicious stored content
    Navigate to the plugin settings pages (usually under Livemesh Widgets or Theme Settings in admin). Review all text inputs, especially widget/element configuration fields, for any unexpected script tags, javascript: URIs, or HTML event handlers (onclick, onerror, etc.).
    Affected if Any plugin setting fields contain raw JavaScript code or HTML script tags that were not intentionally added by an administrator
  5. Verify lsow_admin_ajax handler accessibility
    Send a POST request to /wp-admin/admin-ajax.php with action=lsow_admin_ajax and a minimal data payload (including a valid nonce if needed). Check if the server processes the request without returning a 403 or capability error.
    Affected if The AJAX handler responds to authenticated requests from subscriber-level users without rejecting them for insufficient privileges

A user is affected if the Livemesh SiteOrigin Widgets plugin is installed at version 3.9.2 or lower AND there is at least one user account with Subscriber-level access or higher in the WordPress installation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of the plugin (beyond 3.9.2) which should include proper capability verification and input sanitization. Until then, restrict subscriber-level account creation and monitor for suspicious admin_ajax calls.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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 locally
dbcve dependency scanner

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