dbcve.org
Better Elementor AddonsWordPress extension · Kitforest

CVE-2024-33541

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-04
Fix available
A fix is available. Upgrade to 1.4.2 or later.
See remediation →
71/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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in BetterAddons Better Elementor Addons allows PHP Local File Inclusion.This issue affects Better Elementor Addons: from n/a through 1.4.1.

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

Path traversal vulnerability in Better Elementor Addons plugin allows unauthenticated attackers to perform PHP Local File Inclusion by manipulating path references with directory traversal sequences (../), potentially enabling remote code execution through inclusion of malicious local files.

MitigationUpdate Better Elementor Addons to the latest version that includes the security fix. If no patch is available, disable or remove the plugin until a fixed version is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Better Elementor AddonsWordPress extension
Affected:< 1.4.2

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Better Elementor Addons plugin is installed
    Check your WordPress installation's wp-content/plugins directory for a folder named 'better-elementor-addons' or 'kitforest-better-elementor-addons', or look for the plugin in the WordPress admin under Plugins
    Affected if The plugin folder exists in the plugins directory
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and look for Better Elementor Addons version number, or open the main plugin PHP file and check the 'Version' header in the plugin comments
    Affected if The displayed version is lower than 1.4.2 (e.g., 1.4.1, 1.4.0, 1.3.x, etc.)
  3. Confirm plugin is active
    In WordPress admin, verify the plugin status shows as 'Active' under Plugins > Installed Plugins
    Affected if The plugin is currently activated on the site
  4. Check for suspicious access patterns
    Review web server access logs (Apache/Nginx) for requests containing '../' sequences targeting PHP files, such as '?file=../../../../wp-config.php' or similar path traversal patterns
    Affected if Log analysis reveals unauthenticated requests with directory traversal sequences to the plugin's file inclusion functions

Your site is affected if the Better Elementor Addons plugin is installed, active, and running a version lower than 1.4.2, making it vulnerable to unauthenticated path traversal and local file inclusion attacks.

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
Upgrade available Upgrade to 1.4.2 or later
Fixed in 1.4.2
Interim mitigation

Update Better Elementor Addons to the latest version that includes the security fix. If no patch is available, disable or remove the plugin until a fixed version is released.

Recommended fix High confidence

Better Elementor Addons version 1.4.2

  1. 1. Backup your WordPress site and database before performing any updates
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Locate 'Better Elementor Addons' in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.4.2 or later
  5. 5. Alternatively, download version 1.4.2 from the official WordPress plugin repository
  6. 6. Deactivate and delete the current version if automatic update fails, then upload and install version 1.4.2
  7. 7. Verify the plugin is running version 1.4.2 or later after the update

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

Fix this in Better Elementor Addons 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 the upgrade done

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-2024-33541 — 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-33541 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