CVE
Advanced Custom Fields information disclosure in user field queries
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The Advanced Custom Fields (ACF) plugin for WordPress can be reached over the network by logged-in users with at least subscriber-level access. By injecting extra query parameters, an attacker can bypass field role restrictions and gradually extract sensitive user data, such as administrator email addresses, login names, and private user metadata.
Original description
The Advanced Custom Fields (ACF) plugin for WordPress is vulnerable to incorrect authorization in all versions up to, and including, 6.7.0. This is due to the 'ACF_Ajax_Query::get_args' method returning the user-supplied ''query' array directly without any key whitelisting or validation. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary query parameters to bypass field-configured role restrictions and exfiltrate sensitive user data including administrator email addresses, login names, and private user metadata via blind oracle techniques.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.3/10CVSS 4.3
- No patch5/5No patch listed yet
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-2841 (Advanced Custom Fields (ACF) <= 6.7.0 - Incorrect Authorization to Authenticated (Subscriber+) Sensitive Information Exposure via User…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-2841 (entry last updated 2026-11-18):
Affected:
- wpengine Advanced Custom Fields (ACF®): through 6.7.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-2841 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-2841 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/56bf62d2-1aec-4c61-8e33-919d7b6e94ed?source=cve
- https://plugins.trac.wordpress.org/browser/advanced-custom-fields/trunk/includes/ajax/class-acf-ajax-query.php#L130
- https://plugins.trac.wordpress.org/browser/advanced-custom-fields/trunk/includes/ajax/class-acf-ajax-query-users.php#L178
- https://plugins.trac.wordpress.org/browser/advanced-custom-fields/trunk/includes/fields/class-acf-field-user.php#L44
- https://plugins.trac.wordpress.org/changeset/3473908/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-2841
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-2841"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- wpengine Advanced Custom Fields (ACF®)
through 6.7.0
Evidence 7
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-2841
Is CVE-2026-2841 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-2841?
Advanced Custom Fields (ACF®): through 6.7.0.Source: cve.now feed data