CVE-2024-4565 json
Advanced Custom Fields < 6.3 - Contributor+ Custom Field Access
published 2y ago modified 4mo ago also EUVD-2024-44177
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
The Advanced Custom Fields (ACF) WordPress plugin before 6.3, Advanced Custom Fields Pro WordPress plugin before 6.3 allows you to display custom field values for any post via shortcode without checking for the correct access
Patch / fix
- Unknown Advanced Custom Fields (ACF) 6.3
- Unknown Advanced Custom Fields Pro 6.3
- wpengine advanced_custom_field_pro 6.3
- wpengine advanced_custom_fields 6.3
Is CVE-2024-4565 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/430224c4-d6e3-4ca8-b1bc-b2229a9bcf12/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected products
- Unknown Advanced Custom Fields (ACF)
- Unknown Advanced Custom Fields Pro
- wpengine advanced_custom_field_pro
- wpengine advanced_custom_fields
Classification
- Technology feeds
References
-
wpscan.com
/vulnerability/430224c4-d6e3-4ca8-b1bc-b2229a9bcf12/
exploit, vdb-entry, technical-description, third-party-advisory
Sources
- CVE List CVE-2024-4565
- NVD CVE-2024-4565
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.