dbcve.org
The Pack Elementor AddonsWordPress extension · Webangon

CVE-2024-50453

HIGH · 8.8 CVSS v3.1 Published 2024-10-28
Fix available
A fix is available. Upgrade to 2.1.0 or later.
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
Relative Path Traversal vulnerability in webangon The Pack Elementor addons the-pack-addon allows PHP Local File Inclusion.This issue affects The Pack Elementor addons: from n/a through <= 2.0.9.

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

A relative path traversal vulnerability in The Pack Elementor addons plugin (versions through 2.0.9) allows unauthenticated attackers to manipulate file path parameters to perform Local File Inclusion (LFI), potentially reading sensitive server-side files including PHP source code, configuration files, and credentials.

MitigationImplement strict input validation on file path parameters using basename() and realpath() to resolve and verify paths are within allowed directories, rejecting any input containing directory traversal sequences (..). Additionally, apply proper access controls and consider disabling PHP file inclusion functions if not required.

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
The Pack Elementor AddonsWordPress extension
Affected:< 2.1.0

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. Verify The Pack Elementor Addons plugin is installed
    Locate the plugin directory in the WordPress plugins folder (wp-content/plugins/the-pack-elementor-addons or similar naming) and confirm its presence on the server file system.
    Affected if The plugin directory exists on the server and the plugin is either active or inactive.
  2. Check installed plugin version
    Open the main plugin PHP file (typically main.php, index.php, or the plugin root file) and locate the version declaration in the plugin header comment, or check the version entry in the WordPress plugin admin interface.
    Affected if The installed version is any version prior to 2.1.0 (versions 2.0.9 and earlier are confirmed affected).
  3. Identify if the plugin is active
    Query the WordPress database wp_options table for the active_plugins option, or check through the WordPress admin dashboard plugins list.
    Affected if The plugin appears in the list of active plugins, making the vulnerability accessible to unauthenticated attackers.
  4. Confirm web server accessibility
    Verify the WordPress site is publicly accessible and the plugin endpoints are reachable via HTTP/HTTPS requests without authentication.
    Affected if The site is live and the plugin file inclusion functionality is accessible without authentication, allowing the path traversal vulnerability to be exploited.

A user is affected if The Pack Elementor Addons plugin versions prior to 2.1.0 is installed and active on a publicly accessible WordPress site, enabling unauthenticated attackers to manipulate file path parameters for local file inclusion.

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 2.1.0 or later
Fixed in 2.1.0
Interim mitigation

Implement strict input validation on file path parameters using basename() and realpath() to resolve and verify paths are within allowed directories, rejecting any input containing directory traversal sequences (..). Additionally, apply proper access controls and consider disabling PHP file inclusion functions if not required.

Recommended fix High confidence

2.1.0

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to WordPress admin dashboard > Plugins
  3. 3. Find 'The Pack Elementor Addons' in the installed plugins list
  4. 4. Click 'Update now' if an update is available, or manually update to version 2.1.0
  5. 5. Verify the plugin was updated to version 2.1.0 or later by checking the plugin version number
  6. 6. Test that the website functionality remains intact after the update

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

Fix this in The Pack Elementor Addons Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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