CVE-2024-34762
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 · uneditedVulnerability discovered by executing a planned security audit. Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in WPENGINE INC Advanced Custom Fields PRO allows PHP Local File Inclusion.This issue affects Advanced Custom Fields PRO: from n/a before 6.2.10.
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 · moderate confidenceImproper limitation of a pathname to a restricted directory (path traversal) vulnerability in Advanced Custom Fields PRO plugin for WordPress allows PHP local file inclusion, enabling attackers to read or execute arbitrary files on the server.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Advanced Custom Fields PRO pluginCheck your WordPress installation's wp-content/plugins directory for a folder named 'advanced-custom-fields-pro', or use WP-CLI command: wp plugin list --name='advanced-custom-fields-pro'Affected if The plugin folder 'advanced-custom-fields-pro' exists in your plugins directory
-
Determine installed ACF PRO versionCheck the main plugin file header (usually wp-content/plugins/advanced-custom-fields-pro/acf.php) for the 'Version' comment, or run: wp plugin get advanced-custom-fields-pro --field=versionAffected if The version returned is lower than 6.2.10 (e.g., 6.2.9, 6.2.8, etc.)
-
Verify vulnerability is presentSince this is a path traversal in the plugin's file handling functionality, the vulnerability exists in any version below 6.2.10 - no specific configuration toggle controls this flaw; it is a code-level vulnerability present in the affected versionsAffected if Your installed version is below 6.2.10 and the plugin is active on your WordPress site
You are affected if Advanced Custom Fields PRO is installed and active with a version lower than 6.2.10.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Advanced Custom Fields PRO to version 6.2.10 or later to patch the path traversal vulnerability. Also consider restricting file system permissions and using a Web Application Firewall as a defense-in-depth measure.
6.2.10
- Backup your WordPress site and database before proceeding
- Update Advanced Custom Fields PRO plugin to version 6.2.10 or later through the WordPress admin dashboard (Plugins > Updates)
- Alternatively, upload the updated plugin zip file via Plugins > Add New > Upload Plugin
- Verify the plugin version shows 6.2.10 or higher after updating
- Clear any caching mechanisms if applicable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34762 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-34762 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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