CVE-2026-1572
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 Livemesh Addons for Elementor plugin for WordPress is vulnerable to unauthorized modification of data and Stored Cross-Site Scripting via plugin settings in all versions up to, and including, 9.0. This is due to missing authorization checks on the AJAX handler `lae_admin_ajax()` and insufficient output escaping on multiple checkbox settings fields. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in the plugin settings page that will execute whenever an administrator accesses the plugin settings page granted they can obtain a valid nonce, which can be leaked via the plugin's improper access control on settings pages.
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 confidenceThe Livemesh Addons for Elementor plugin for WordPress has a missing authorization vulnerability in the `lae_admin_ajax()` AJAX handler that allows any authenticated user with Subscriber-level access or higher to modify plugin settings. Combined with insufficient output escaping on checkbox settings fields, this enables stored Cross-Site Scripting (XSS) where malicious scripts are injected into plugin settings and execute when administrators access the settings page. The attack is facilitated by improper access control that leaks valid nonces.
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 Livemesh Addons for Elementor plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find 'Livemesh Addons for Elementor'. Compare the installed version to 9.1 - versions below 9.1 are affected.Affected if Installed version is lower than 9.1
-
Confirm user registration is enabledIn WordPress admin, go to Settings > General and check if 'Membership' > 'Anyone can register' is enabled. Also verify the 'New User Default Role' is set to Subscriber or a higher role.Affected if User registration is enabled with Subscriber or higher default role
-
Test AJAX endpoint accessibilitySend an authenticated AJAX request to wp-admin/admin-ajax.php with action=lae_admin_ajax using a low-privilege (Subscriber) account. Inspect the response for successful plugin settings modification.Affected if AJAX handler responds to authenticated requests from Subscriber-level users without proper authorization checks
-
Inspect plugin settings for injected scriptsNavigate to the Livemesh Addons settings page (usually under Elementor > Livemesh Addons). View page source or inspect checkbox settings fields for any suspicious script tags or event handlers.Affected if Plugin settings contain unsanitized script content or event handlers that could indicate exploited XSS
A user is affected if the Livemesh Addons for Elementor plugin version is below 9.1 and the site allows Subscriber-level or higher user registration, enabling unauthenticated or low-privilege users to inject malicious scripts via the AJAX handler.
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 to version 9.1 or later which includes authorization checks, output escaping fixes, and proper nonce handling. Until the update is applied, consider disabling the plugin or restricting user registration to prevent lower-privileged users from accessing the dashboard.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1572 — 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-1572 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