CVE-2024-9529: Secure Custom Fields < 6.3.6.3 - Admin+ Remote Code Execution
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.43% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Unknown Advanced Custom Fields Pro 6.3.9; Unknown Secure Custom Fields 6.3.6.3, 6.3.9.
Low priority for now. Upgrade to Unknown Advanced Custom Fields Pro 6.3.9; Unknown Secure Custom Fields 6.3.6.3, 6.3.9 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The Secure Custom Fields WordPress plugin before 6.3.9, Secure Custom Fields WordPress plugin before 6.3.6.3, Advanced Custom Fields Pro WordPress plugin before 6.3.9 does not prevent users from running arbitrary functions through its setting import functionalities, which could allow high privilege users such as admin to run arbitrary PHP functions.
- Published
- Nov 15, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 38th percentile
- CWE
- CWE-94
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| advancedcustomfields | advanced custom fields | cpe:2.3:a:advancedcustomfields:advanced_custom_fields |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (WPScan). Independent of NVD's CPE analysis and usually ahead of it.
Unknown Advanced Custom Fields Pro
- before 6.3.9affected · semver
Unknown Secure Custom Fields
- 6.3.7 and later · before 6.3.9affected · semver
- before 6.3.6.3affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- advancedcustomfields advanced custom fieldsbefore 6.3.9
Same product
advancedcustomfields: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-30777WordPress Advanced Custom Fields / Advanced Custom Fields PRO plugins <= 6.1.5 vulnerable to Cross Site Scripting (XSS)36Monitor
- CVE-2023-1196Advanced Custom Fields - Contributor+ PHP Object Injection35Monitor
- CVE-2022-2594Advanced Custom Fields 5.0-5.12.2 - Unauthenticated File Upload35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2022-40696Jan 8, 2024 · WordPress Advanced Custom Fields Plugin 3.1.1-6.0.2 is vulnerable to Sensitive Data Exposure30Monitor
- ← EarlierCVE-2023-6701Feb 5, 2024 · Advanced Custom Fields <= 6.2.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via Custom Field21Monitor
- ← EarlierCVE-2024-4565Jun 20, 2024 · Advanced Custom Fields < 6.3 - Contributor+ Custom Field Access26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Unknown Advanced Custom Fields Pro | 6.3.9 | Vendor (CNA) |
| Unknown Secure Custom Fields | 6.3.6.3 | Vendor (CNA) |
| Unknown Secure Custom Fields | 6.3.9 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Automattic Security Teamfinder
- WPScancoordinator
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →