What this page helps you verify fast
This hub clusters tracked records for Advanced Custom Fields Pro so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
Review known vulnerability records for the WordPress plugin Advanced Custom Fields Pro (`advanced-custom-fields-pro`), including severity, CVE references, affected versions, and patch status.
Recent tracked CVEs on this page include CVE-2024-37249, CVE-2024-37251 and CVE-2024-37250, so operators can jump from disclosure to patch validation without scanning the full feed first.
Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.
Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.
Affected range: Versions up to 6.2.9. Fixed version: 6.2.10.
Affected range: Versions up to 6.2.9. Fixed version: 6.2.10.
Affected range: Versions before 5.9.1. Fixed version: 5.9.1.
Affected range: Versions up to 6.3.1. Fixed version: 6.3.2.
Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.
| Tracked CVE | Issue Type | Affected Versions | Fixed Version | CVSS |
|---|---|---|---|---|
|
CVE-2024-34761
Advanced Custom Fields Pro <= 6.2.9 - Authenticated (Contributor+) Code Injection
|
Vulnerability | Versions up to 6.2.9 | 6.2.10 | CVSS 9.9 |
|
CVE-2024-34762
Advanced Custom Fields Pro <= 6.2.9 - Authenticated (Contributor+) Local File Inclus...
|
Local File Inclusion | Versions up to 6.2.9 | 6.2.10 | CVSS 8.8 |
|
CVE-2021-24241
Advanced Custom Fields Pro <= 5.9.0 - Reflected Cross-Site Scripting
|
Cross-Site Scripting | Versions before 5.9.1 | 5.9.1 | CVSS 6.1 |
|
CVE-2024-37250
Advanced Custom Fields Pro <= 6.3.1 - Missing Authorization
|
Vulnerability | Versions up to 6.3.1 | 6.3.2 | CVSS 5.4 |
|
CVE-2024-37250
Advanced Custom Fields Pro <= 6.3.1 - Missing Authorization
|
Vulnerability | Versions up to 6.3.1 | 6.3.2 | CVSS 5.4 |
|
CVE-2024-37249
Advanced Custom Fields PRO < 6.3.2 - Missing Authorization
|
Vulnerability | Versions before 6.3.2 | 6.3.2 | CVSS 4.3 |
|
CVE-2024-37251
Advanced Custom Fields Pro <= 6.3.1 - Cross-Site Request Forgery
|
Cross-Site Request Forgery | Versions up to 6.3.1 | 6.3.2 | CVSS 4.3 |
Advanced Custom Fields Pro <= 6.2.9 - Authenticated (Contributor+) Code Injection
Advanced Custom Fields Pro <= 6.2.9 - Authenticated (Contributor+) Local File Inclusion
Advanced Custom Fields Pro <= 5.9.0 - Reflected Cross-Site Scripting
Advanced Custom Fields Pro <= 6.3.1 - Missing Authorization
Advanced Custom Fields Pro <= 6.3.1 - Missing Authorization
Advanced Custom Fields PRO < 6.3.2 - Missing Authorization
Advanced Custom Fields Pro <= 6.3.1 - Cross-Site Request Forgery
This hub clusters tracked records for Advanced Custom Fields Pro so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
These recent records surface the CVE strings, patch cues, and direct report links most operators need first.
The Advanced Custom Fields PRO plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in versions up to 6.3.2. This makes it possible for a...
The Advanced Custom Fields Pro plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 6.3.1. This is due to missing or incorrect nonce validat...
The Advanced Custom Fields Pro plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to, and including, 6.3.1. This mak...
Sorted by latest disclosure date so newly published issues surface first.
The Advanced Custom Fields PRO plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in versions up to 6.3.2. This makes it possible for authenticated attackers, with contributor-level access and above, to perform an unauthorize...
The Advanced Custom Fields Pro plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 6.3.1. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unau...
The Advanced Custom Fields Pro plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to, and including, 6.3.1. This makes it possible for authenticated attackers, with contributor-level access and above, to pe...
The Advanced Custom Fields Pro plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to, and including, 6.3.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to per...
The Advanced Custom Fields Pro plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 6.2.9. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary files on the server...
The Advanced Custom Fields Pro plugin for WordPress is vulnerable to Code Injection in all versions up to, and including, 6.2.9. This makes it possible for authenticated attackers, with contributor-level access and above, to execute code on the server.
The Advanced Custom Fields PRO plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in versions 6.1 through 6.1.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-lev...
The Advanced Custom Fields Pro WordPress plugin before 5.9.1 did not properly escape the generated update URL when outputting it in an attribute, leading to a reflected Cross-Site Scripting issue in the update settings page.