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

CVE-2024-5348

HIGH · 8.8 CVSS v3.1 Published 2024-06-01
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 Elements For Elementor plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.1 via the 'beforeafter_layout' attribute of the beforeafter widget, the 'eventsgrid_layout' attribute of the eventsgrid and list widgets, the 'marquee_layout' attribute of the marquee widget, the 'postgrid_layout' attribute of the postgrid widget, the 'woocart_layout' attribute of the woocart widget, and the 'woogrid_layout' attribute of the woogrid widget. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

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 Elements For Elementor WordPress plugin is vulnerable to Local File Inclusion (LFI) in all versions up to 2.1. The vulnerability exists in multiple widgets (beforeafter, eventsgrid, list, marquee, postgrid, woocart, woogrid) through various layout attributes (beforeafter_layout, eventsgrid_layout, marquee_layout, postgrid_layout, woocart_layout, woogrid_layout). Authenticated attackers with Contributor-level access or higher can include and execute arbitrary files on the server, leading to PHP code execution.

MitigationUpdate the Elements For Elementor plugin to the latest version once available. If no update exists, disable the plugin immediately and review server file permissions and access controls to limit the impact of LFI attacks.

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. Identify Elements For Elementor plugin installation
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Locate 'Elements For Elementor' and note the installed version number.
    Affected if The plugin is installed and the version is 2.1 or lower.
  2. Verify plugin version against affected range
    Compare the installed version to the affected range. All versions up to and including 2.1 are vulnerable.
    Affected if The installed version is 2.1 or any earlier version.
  3. Check for use of vulnerable widgets
    Review pages/posts using Elementor editor. Look for widgets: beforeafter, eventsgrid, list, marquee, postgrid, woocart, and woogrid.
    Affected if Any of these seven widgets are present and active on the site.
  4. Inspect widget layout attributes in database
    Query the wp_postmeta table for meta_key values containing layout attributes: _beforeafter_layout, _eventsgrid_layout, _marquee_layout, _postgrid_layout, _woocart_layout, or _woogrid_layout. Run: SELECT * FROM wp_postmeta WHERE meta_key LIKE '%_layout%';
    Affected if Records exist with these layout meta_keys, indicating vulnerable attributes are configured.
  5. Identify Contributor-level or higher users
    In WordPress admin > Users, review user roles. Check for accounts with Contributor, Author, Editor, or Administrator roles.
    Affected if Any authenticated user with Contributor-level access or higher exists on the site.

A user is affected if the Elements For Elementor plugin version is 2.1 or lower AND any of the vulnerable widgets (beforeafter, eventsgrid, list, marquee, postgrid, woocart, woogrid) are in use on the site, allowing an authenticated Contributor+ user to exploit LFI through layout attributes.

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 the Elements For Elementor plugin to the latest version once available. If no update exists, disable the plugin immediately and review server file permissions and access controls to limit the impact of LFI attacks.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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