dbcve.org
The Pack Elementor AddonsWordPress extension · Webangon

CVE-2024-38768

HIGH · 8.8 CVSS v3.1 Published 2024-08-01
Fix available
A fix is available. Upgrade to 2.0.8.7 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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Webangon The Pack Elementor addons allows PHP Local File Inclusion, Path Traversal.This issue affects The Pack Elementor addons: from n/a through 2.0.8.6.

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 The Pack Elementor addons plugin (versions up to 2.0.8.6) allows remote attackers to read arbitrary files on the server via improper validation of file paths in PHP local file inclusion functionality, potentially exposing sensitive configuration files, credentials, and source code.

MitigationUpdate to the latest patched version of The Pack Elementor addons. If no patched version is available, disable the plugin or implement WAF rules to block path traversal sequences (../) in HTTP requests.

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.0.8.7

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 plugin is installed
    Check your WordPress installation's wp-content/plugins directory for a folder named 'the-pack' or look for 'The Pack Elementor Addons' in the WordPress plugin admin interface under Plugins > Installed Plugins
    Affected if The plugin folder 'the-pack' exists in wp-content/plugins
  2. Identify installed plugin version
    If the plugin is installed, check the main PHP file header (typically the-pack/main.php or the-pack/index.php) for the 'Version' comment, or view the plugin details in WordPress admin under Plugins > Installed Plugins > The Pack Elementor Addons
    Affected if The reported version is lower than 2.0.8.7 (e.g., 2.0.8.6, 2.0.7, 2.0.5, etc.)
  3. Check if PHP file inclusion functionality is accessible
    Review the plugin's PHP files for functions that handle file paths (such as include, require, file_get_contents, readfile) and verify if any endpoint or parameter accepts user input for file paths - look for code patterns like $_GET['file'] or similar being passed to file inclusion functions
    Affected if The plugin contains code that accepts file path parameters from user input and passes them to PHP inclusion functions without proper sanitization (specifically checking for ../ sequences)
  4. Review web server access logs for path traversal attempts
    Search your web server access logs (Apache error.log, Nginx access.log) for requests containing '../' sequences targeting the plugin's PHP files, for example: grep -r "../" /var/log/apache2/ | grep the-pack
    Affected if Any log entries show path traversal patterns (../) in requests to the plugin endpoints, indicating active exploitation attempts

A user is affected if The Pack Elementor Addons plugin version is below 2.0.8.7 AND the vulnerable file inclusion functionality exists and is accessible.

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.0.8.7 or later
Fixed in 2.0.8.7
Interim mitigation

Update to the latest patched version of The Pack Elementor addons. If no patched version is available, disable the plugin or implement WAF rules to block path traversal sequences (../) in HTTP requests.

Recommended fix High confidence

The Pack Elementor Addons version 2.0.8.7

  1. Backup your WordPress site and database.
  2. Navigate to the WordPress Admin Dashboard > Plugins > Installed Plugins.
  3. Locate 'The Pack Elementor Addons' in the list.
  4. Update the plugin to version 2.0.8.7 or the latest available version.
  5. Verify the plugin version matches the fixed release.

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

Fix this in The Pack Elementor Addons Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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