dbcve.org
Element PackWordPress extension · Bdthemes

CVE-2024-33568

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-04
Fix available
A fix is available. Upgrade to after 7.7.4 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'), Deserialization of Untrusted Data vulnerability in BdThemes Element Pack Pro allows Path Traversal, Object Injection.This issue affects Element Pack Pro: from n/a before 7.19.3.

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

BdThemes Element Pack Pro WordPress plugin before version 7.19.3 contains a path traversal vulnerability combined with unsafe deserialization that allows Object Injection. An attacker could exploit this to access files outside the restricted directory and potentially execute arbitrary code through deserialized objects.

MitigationUpdate Element Pack Pro to version 7.19.3 or later. If patching is not immediately possible, restrict administrative access to trusted users and monitor for suspicious file access patterns.

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
Element PackWordPress extension
Affected:<= 7.7.4

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 Element Pack Pro plugin is installed
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Element Pack Pro' or 'BdThemes Element Pack' in the plugin list. Alternatively, check the wp-content/plugins directory for a folder named 'bdthemes-element-pack' or similar.
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed version
    In WordPress admin, click on the plugin name to view details and locate the version number. Alternatively, open the main plugin PHP file (usually in wp-content/plugins/bdthemes-element-pack/) and look for a version constant or header comment.
    Affected if The displayed version number is 7.7.4 or lower
  3. Identify vulnerable deserialization entry points
    Search the plugin directory for PHP files containing 'unserialize', 'base64_decode', or file inclusion functions like 'include', 'require', 'file_get_contents' that accept user input without sanitization. Focus on AJAX handlers or callback files.
    Affected if Files with unsafe deserialization routines are present and accessible via web requests
  4. Check for path traversal vulnerable code
    Examine PHP files in the plugin for functions that accept file paths from request parameters (like $_GET, $_POST) without proper validation. Look for patterns like file operations using user-controlled paths.
    Affected if Code allowing traversal sequences (../) in file paths without validation is found
  5. Monitor for suspicious file access patterns
    Review web server access logs for requests to the plugin directory containing '../' sequences or unusual base64-encoded parameters. Check for repeated access to potential deserialization endpoints.
    Affected if Log analysis reveals traversal attempts or suspicious encoded parameters targeting the plugin

A user is affected if BdThemes Element Pack Pro is installed with version 7.7.4 or lower and the plugin exposes vulnerable endpoints accessible to attackers.

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 a release after 7.7.4
Interim mitigation

Update Element Pack Pro to version 7.19.3 or later. If patching is not immediately possible, restrict administrative access to trusted users and monitor for suspicious file access patterns.

Recommended fix Moderate confidence

Element Pack Pro: 7.19.3 or later; Element Pack (free): latest version after 7.7.4

  1. 1. Back up your WordPress site and database before performing any updates.
  2. 2. Navigate to the WordPress dashboard and go to Plugins > Installed Plugins.
  3. 3. Locate 'Element Pack' (or 'Element Pack Pro') in the plugin list.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Verify the update completed successfully by checking the plugin version.
  6. 6. Test critical site functionality to ensure the plugin continues to work correctly after the update.

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

Fix this in Element Pack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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