Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site with two visitor-targeted ACF Extended forms
-
DeliverySubmit update-user request with mismatched auth/execution target
-
ExploitBypass administrator-account guard via inconsistent target resolution
-
ExecutionOverwrite administrator account and receive valid session
-
ImpactFull administrator takeover of WordPress site
Vulnerability Assessment
| Weakness |
CWE
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a specific, non-default deployment: the site must publish two separate front-end form configurations in ACF Extended's Forms module, each using the update-user action, whose targets are mapped to visitor-submitted values. The flaw is that the update-user target is resolved inconsistently between the stage that authorises the request and the stage that executes it, letting an unauthenticated visitor bypass the guard protecting administrator accounts. Limiting factors: both forms must exist and expose visitor-controlled target mapping (reflected in CVSS AC:H); sites that do not use front-end user-update forms, or that do not map targets to visitor input, are not exploitable. No authentication or user interaction is required once that configuration is present (PR:N/UI:N). |
| Impact | This is a genuinely high-impact but conditionally-exploitable flaw, and the signals are coherent rather than conflicting. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/C:H/I:H/A:H, base 8.1) describes a network-reachable, unauthenticated issue whose AC:H reflects a real, non-default precondition: the attack only works when the site publishes two separate front-end form configurations whose targets are mapped to visitor-submitted values. CISA SSVC reinforces this nuance - Exploitation: none (no observed in-the-wild activity), Automatable: no (the dual-form prerequisite and inconsistent-resolution logic cannot be sprayed broadly), but Technical Impact: total, consistent with full administrator account takeover and an issued valid session. There is no CISA KEV listing and no EPSS score was supplied, so widespread opportunistic exploitation cannot be inferred from the data. The vuln.today priority label is 'this_week' (not act_now/emergency), which aligns with: severe outcome if the vulnerable configuration exists, but gated behind a specific deployment pattern rather than default-config mass exploitation. Net: a real priority for the subset of sites running ACF Extended's front-end Forms with the described update-user mapping, and lower practical risk for the majority that do not expose that configuration. |
| Exploit ScenarioDerived | On a WordPress site running ACF Extended with two front-end forms whose update-user targets are driven by visitor-submitted values, an unauthenticated visitor submits a request crafted so the target account resolved during authorization differs from the one acted upon during execution, bypassing the guard that protects administrator accounts. The attacker thereby updates the administrator account and is issued a valid authenticated session for it, achieving full site takeover. No public exploit code is identified at time of analysis; the issue was reported by WPScan. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 23, 2026
Unauthenticated takeover of a site administrator account is possible in the Advanced Custom Fields: Extended and Extended PRO WordPress plugins before 0.9.2.8 through the front-end Forms module. The update-user action resolves its target inconsistently between the stage that authorises the request and the stage that executes it, so an attacker can direct the update at an administrator account and be issued a valid session for it. The configuration prerequisite is narrow but explicit: the site must publish two separate front-end form configurations whose update-user targets are mapped to visitor-submitted values, which is reflected in the high attack complexity of the assessed CVSS vector. No public exploit code was identified at time of analysis, SSVC records no observed exploitation, and no KEV or EPSS data was supplied; the vendor has released a patch in 0.9.2.8.
RemediationAI
Vendor-released patch: update Advanced Custom Fields: Extended (free) and Advanced Custom Fields: Extended PRO to 0.9.2.8 or later, per the WPScan advisory at https://wpscan.com/vulnerability/eccfab3c-e7cc-4623-9c20-4cd6c32f8422/. Because the vulnerable path depends on a specific configuration rather than on every installation, sites that cannot patch immediately should audit the Forms module and remove or disable any front-end form that uses the update-user action, and in particular ensure no site exposes two separate such forms with their targets mapped to visitor-submitted values - removing either of the paired forms closes the documented exploitation path, at the cost of losing that front-end user-update workflow. Since no authentication or user interaction is required once the prerequisite configuration exists, blocking access to the affected front-end forms at the web server or WAF layer is a further stopgap, with the trade-off that legitimate front-end submissions through those forms will also be blocked. Applying the 0.9.2.8 update remains the complete fix and should be treated as this-week priority work on any site running the plugin with front-end user-update forms.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw lives in the Forms module of the ACF Extended plugin for WordPress, where a front-end form can be configured with an update-user action that modifies an existing WordPress user account. CWE-269 (Improper Privilege Management) applies because the code does not consistently resolve which user account the action targets: the identity checked when the request is authorised differs from the identity used when the update is carried out. That divergence lets an unauthenticated visitor satisfy the guard for one account while causing the update - and the resulting authenticated session - to land on an administrator account, effectively skipping the privilege boundary that is supposed to protect administrator users. The assessed vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, network-reachable with no privileges or user interaction required, but only when the site publishes two distinct front-end forms whose update-user targets are bound to visitor-supplied values; sites without that exact configuration, or with only a single such form, are not exploitable through this path. The trigger sequence beyond that inconsistent target resolution is not described in the available sources, and no CPE identifiers were provided, so product scoping must rely on the vendor advisory and the EUVD version ranges.
Know when WordPress gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Unauthenticated and network-reachable (PR:N/AV:N), but AC:H because it needs a specific dual front-end-form configuration; administrator takeover yields total C/I/A impact.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
3DescriptionCVE.org
The Advanced Custom Fields: Extended WordPress plugin before 0.9.2.8, Advanced Custom Fields: Extended PRO WordPress plugin before 0.9.2.8 does not resolve the target of the update-user action in its front-end Forms module consistently between the stage that authorises the request and the stage that carries it out, which allows unauthenticated visitors to bypass the guard protecting administrator accounts, take over the site administrator's account and be issued a valid session for it. Exploitation requires the site to publish two separate front-end form configurations whose targets are mapped to visitor-submitted values.
Executive ViewAI
CVE-2026-94268 is a high-severity vulnerability in the Advanced Custom Fields: Extended and Extended PRO WordPress plugins (versions before 0.9.2.8) that can allow an unauthenticated attacker to take over a site administrator account. This affects organizations running these plugins with specific front-end form configurations. While no public exploit was identified at time of analysis, a successful attack could lead to full site compromise, data breach, and reputational damage. Leadership should prioritize patching to mitigate this risk.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r
EUVD-2026-108605
GHSA-5c6h-7vg8-f3f2
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB