dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-34761

HIGH · 8.5 CVSS v3.1 Published 2024-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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
Vulnerability discovered by executing a planned security audit. Improper Control of Generation of Code ('Code Injection') vulnerability in WPENGINE INC Advanced Custom Fields PRO allows Code Injection.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 confidence

Code Injection vulnerability in Advanced Custom Fields PRO plugin for WordPress allows authenticated attackers to inject and execute arbitrary code. The vulnerability exists in versions before 6.2.10 and can be exploited through the plugin's field configuration mechanisms.

MitigationUpdate Advanced Custom Fields PRO to version 6.2.10 or later to remediate this vulnerability. Review user access controls and audit existing field configurations for any malicious modifications.

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
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Advanced Custom Fields PRO is installed
    Check the WordPress plugins directory for the 'advanced-custom-fields-pro' folder, or list installed plugins via wp-cli: wp plugin list --status=active --field=name
    Affected if The plugin folder 'advanced-custom-fields-pro' exists in wp-content/plugins/ and appears in the active plugins list
  2. Check installed ACF PRO version
    Read the main plugin file header: wp-content/plugins/advanced-custom-fields-pro/acf.php, or use wp-cli: wp plugin get advanced-custom-fields-pro --field=version
    Affected if The reported version is lower than 6.2.10 (e.g., 6.2.9, 6.2.8, 6.2.7, etc.)
  3. Confirm plugin is active
    Check WordPress options table for 'acf_pro_version' option, or verify the plugin is enabled in wp-admin > Plugins
    Affected if The plugin is active and running a version before 6.2.10
  4. Audit user roles with field configuration access
    Review WordPress user roles that have 'manage_options' capability or custom capabilities related to ACF field groups (acf-field-group, acf-field)
    Affected if Non-admin or untrusted users have permission to create or edit ACF field groups

Your environment is affected if Advanced Custom Fields PRO is installed and active with a version earlier than 6.2.10, especially if lower-privileged users can access field configuration settings.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Advanced Custom Fields PRO to version 6.2.10 or later to remediate this vulnerability. Review user access controls and audit existing field configurations for any malicious modifications.

Recommended fix Moderate confidence

6.2.10 or later

  1. 1. Back up your WordPress site database and files before performing any updates
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find 'Advanced Custom Fields PRO' in the plugin list
  5. 5. If an update is available, click 'Update Now' to update to the latest version (6.2.10 or later)
  6. 6. Alternatively, download the latest version from the official WordPress plugin repository or your WPENGINE account
  7. 7. Verify the plugin version after update by checking Plugins > Installed Plugins
  8. 8. Test your custom field configurations to ensure functionality is intact

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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 locally
dbcve dependency scanner

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