dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2026-1620

HIGH · 8.8 CVSS v3.1 Published 2026-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 Elementor plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 9.0. This is due to insufficient sanitization of the template name parameter in the `lae_get_template_part()` function, which uses an inadequate `str_replace()` approach that can be bypassed using recursive directory traversal patterns. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary files on the server, allowing the attacker to include and execute local files via the widget's template parameter granted they can trick an administrator into performing an action or install Elementor.

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

Local File Inclusion vulnerability in Livemesh Addons for Elementor WordPress plugin where the `lae_get_template_part()` function uses inadequate `str_replace()` sanitization on the template name parameter, allowing bypass via recursive directory traversal patterns (e.g., ....//). Authenticated users with Contributor-level access and above can include and execute arbitrary files on the server.

MitigationUpgrade to version 9.1 or later when available; until then, implement strict input validation on the template parameter to reject directory traversal sequences and consider restricting contributor-level template access via plugin configuration or additional access controls.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Locate the Livemesh Addons for Elementor plugin installation
    Check the WordPress plugins directory (wp-content/plugins/livemesh-elementor-addons/) for the plugin folder and identify the main plugin file (usually livemesh-elementor-addons.php)
    Affected if The plugin folder and files are present on the server
  2. Determine the installed plugin version
    Open the main plugin file and locate the Version header in the plugin comment block, or check readme.txt for the 'Stable tag' entry
    Affected if The version is lower than 9.1 (the fixed version)
  3. Verify the plugin is active on the WordPress site
    Query the WordPress database wp_options table for option_name='active_plugins' and check if 'livemesh-elementor-addons' appears in the serialized array, or use wp-cli: wp plugin list --status=active --name='livemesh-elementor-addons'
    Affected if The plugin appears in the active plugins list
  4. Confirm Contributor-level user access exists
    Query the WordPress database wp_usermeta table for users with wp_capabilities meta containing 'contributor' role (a:1:{s:10:"contributor";b:1;}), or check User roles in WordPress admin dashboard
    Affected if At least one user account has Contributor-level role or higher privileges
  5. Inspect the vulnerable lae_get_template_part function
    Examine the plugin source code file containing lae_get_template_part() function and verify it uses str_replace() for sanitization without proper validation against directory traversal patterns
    Affected if The function uses str_replace() without rejecting sequences like '....//' or '../' patterns

The environment is affected if Livemesh Addons for Elementor is installed, active, and running a version before 9.1 while having at least one Contributor-level user account on the 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

Upgrade to version 9.1 or later when available; until then, implement strict input validation on the template parameter to reject directory traversal sequences and consider restricting contributor-level template access via plugin configuration or additional access controls.

Recommended fix Moderate confidence

Livemesh Addons for Elementor v9.1 or later

  1. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  2. Locate 'Livemesh Addons for Elementor' plugin
  3. Check the current installed version (vulnerable if 9.0 or earlier)
  4. Update the plugin to the latest available version (9.1 or higher)
  5. Verify the update completed successfully
  6. Confirm the new version is 9.1 or later which contains the patch for the LFI vulnerability

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-1620 — 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-1620 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