Skip to content
eastbaycyber

CVE-2026-8809: ACFE WordPress Privilege Escalation

CVSS · Critical
9.8
In CISA KEV
No
Published
Nov 17
Patch SLA & TriageVector: Network
24 to 48 hours

Critical CVSS (9.8) reachable over network.

Exposure:
Control:
CVSS v3.1 Blast RadiusScore: 9.8
Decode Vector & Sub-Scores →
CVE explainers 10 min read
Security Research Desk Source-checked
Auto-checked against the official CVE record · Human-reviewed after publishing · Updated 2026-11-17
▲ Escalation ViewOne CVE, briefed at three altitudes — skim the Brief, weigh the Impact, or work the Runbook. The way a SOC actually reads it.
CISOBrief · 30-second brief

TL;DR - CVE-2026-8809 is a reported CVSS 9.8 unauthenticated privilege-escalation flaw in Advanced Custom Fields: Extended. - Sites with a public ACFE frontend form using the Create User action may allow administrator account creation. - No confirmed active exploitation or public proof of concept is known from the supplied sources. - Affected sites should upgrade, disable the relevant functionality, or remove the plugin while investigating exposure.

Summary

CVE-2026-8809 affects the WordPress Advanced Custom Fields: Extended plugin, also identified as acf-extended and associated with publisher identifier hwk-fr. Versions from 0 through and including 0.9.2.5 are reported as affected.

The issue is a validation bypass that can permit an unauthenticated attacker to create a new WordPress administrator account when a qualifying public frontend form is available. This WordPress privilege escalation issue is especially serious because an attacker does not need an existing WordPress account when the vulnerable form is publicly reachable.

Field Value
CVE CVE-2026-8809
CWE CWE-269: Improper Privilege Management
CVSS 9.8 Critical
CVSS vector Not supplied in the available NVD response; verify the current NVD record before publication or scoring automation
Attack vector Network
Authentication required None, when the vulnerable public form prerequisite exists
Privileges required None
User interaction Not required based on the described attack path
Affected versions 0 through 0.9.2.5, inclusive
Patch available A related WordPress.org changeset exists, but the exact fixed release was not independently confirmed
CISA KEV No
Confirmed exploitation Not established from the supplied sources
Public PoC No verified working PoC identified

The vulnerability is critical because successful exploitation changes the security boundary of the WordPress installation. An attacker who creates an administrator account can generally manage content, install or modify plugins, alter site configuration, access sensitive data, and potentially execute server-side code through legitimate WordPress administrative functionality.

The exposure condition is narrower than “every installation of the plugin is remotely exploitable.” The target must expose a public ACFE frontend form configured with a Create User action and a mapped role field. Internet-facing sites meeting that condition should still be treated as high risk because exploitation does not require an existing WordPress account.

Analyst’s Take: Prioritize sites where an affected plugin version and a public Create User form overlap. The absence of confirmed exploitation or a public PoC does not offset the consequence of unauthenticated administrator creation.

For related vulnerability terminology, see our SIEM hardening best practices glossary.

AnalystImpact · assess the risk

Root Cause

The root cause is an improper trust decision in the plugin’s after_validate_save_post() processing. The function unconditionally trusts the attacker-controlled _acf_post_id POST parameter. According to the vulnerability description, that value is not protected by authentication or an integrity check before it selects a cleanup path.

That cleanup path silently removes validation errors that do not begin with the acfe: prefix. Two security-relevant errors can therefore be suppressed:

  1. The role allow-list validation error generated by acfe_field_user_roles::validate_front_value().
  2. The administrator-role capability guard generated by acfe_module_form_action_user::validate_action().

Once these checks are bypassed, the user-creation action can reach wp_insert_user() with an attacker-supplied administrator role argument. The result is a newly created WordPress user with administrator-level privileges.

This is a privilege-management failure rather than a conventional memory-safety issue. The application performs validation, but a client-controlled parameter causes the validation result to be altered before the sensitive operation completes. Defenders should review both the plugin version and the site’s form configuration; version scanning alone may not identify whether the vulnerable code path is publicly reachable.

Technical Notes

The relevant code areas identified in the NVD references include:

  • after_validate_save_post() in includes/hooks.php
  • Advanced Custom Fields Extended module logic in includes/module-acf.php
  • User-action validation in includes/modules/form/module-form-action-user.php
  • Frontend form processing in includes/modules/form/module-form-front.php

The supplied research material references tag 0.9.2.4 and WordPress.org changeset 3551665. The cited Trac requests returned HTTP 403 during retrieval, so the complete patch and exact fixed release could not be independently validated.

Who’s Exposed

The directly affected product is Advanced Custom Fields: Extended. The reported affected range is all versions from 0 through and including 0.9.2.5. Sites running a later version should still verify the installed version against the vendor’s release information because the exact first fixed release was not established from the available evidence.

The most important exposure qualifier is configuration. A site is particularly at risk when it has an internet-accessible ACFE frontend form configured with a Create User action that maps a role field. A private administrative form, a site without the plugin, or an installation where the relevant frontend user-creation functionality is disabled does not present the same described attack path.

Exposure condition Risk interpretation
Plugin version 0 through 0.9.2.5, public Create User form, role field mapped High priority; treat as potentially exploitable
Affected plugin version, no public frontend user-creation form Vulnerable code may be installed, but the described unauthenticated path may not be reachable
Plugin disabled or removed Plugin attack path unavailable, subject to other site compromise routes
Version newer than 0.9.2.5 Verify release notes and fix status; do not assume safety without confirmation
Public form protected by authentication or network controls Exposure is reduced, but review whether controls are consistently enforced

Organizations operating WordPress multisite, membership, registration, onboarding, or community workflows should inventory every site and subsite. Forms may be embedded in less-visible landing pages or custom templates, so checking only the homepage is insufficient.

Severity Breakdown

CVE-2026-8809 has a reported CVSS score of 9.8 Critical. The available NVD response did not include the vector string, so the exact component values should be confirmed directly in the current NVD record before using them in automated risk calculations or compliance reports.

The described attack characteristics indicate a remote, unauthenticated attack with severe impact. The attacker does not need an existing WordPress account when the qualifying public form is exposed. Successful exploitation can create a new administrator account, enabling broad control over WordPress content, users, plugins, themes, settings, and potentially stored secrets.

CVSS-related characteristic Assessment from available evidence
Attack vector Network
Attack complexity Not independently confirmed from the supplied vector; the prerequisite is a qualifying public form
Privileges required None
User interaction Not indicated as required
Scope Exact vector component not supplied; assess using the current NVD record
Confidentiality impact High potential impact after administrator creation
Integrity impact High potential impact after administrator creation
Availability impact High potential impact after administrator creation

The configuration prerequisite should not be mistaken for meaningful attacker authentication. A publicly reachable form can be discovered through crawling, page enumeration, JavaScript inspection, search indexing, or WordPress content analysis. If the form accepts user-controlled fields and invokes the vulnerable Create User action, the attacker may be able to submit the request directly.

Exploitation Status

CVE-2026-8809 is not listed in the CISA Known Exploited Vulnerabilities catalog according to the supplied CISA response. No CISA dateAdded, due date, required action, or ransomware-campaign flag is available. CISA has not cataloged the CVE as a confirmed known-exploited vulnerability; that does not prove exploitation cannot occur.

No confirmed in-the-wild exploitation was established from the supplied NVD or CISA KEV data. Likewise, no verified public GitHub exploit repository or working proof of concept was identified in the supplied search results. However, the NVD description identifies the relevant POST parameter, validation behavior, function names, and source locations. That information may reduce the effort needed for a researcher or attacker to reproduce the issue.

Defenders should use the absence of a confirmed PoC as a prioritization input, not as a reason to defer remediation. A public form that allows unauthenticated administrator creation represents a serious control failure even if exploitation telemetry is currently absent.

Sources

The primary vulnerability and product information is attributed to Wordfence in the NVD record:

The NVD record identifies the following WordPress.org source references:

The referenced Trac requests returned HTTP 403 in the supplied retrieval attempts. Consequently, the changeset was treated as evidence that a related source change exists, not as independently verified proof of the exact fixed release or complete patch contents.

The supplied timeline records NVD publication on 2026-05-28 and last modification on 2026-07-21. CISA KEV status was reported as on_kev: false. No confirmed active exploitation or verified public proof of concept was established from the available sources.

This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.

ResponderRunbook · act now

Detection Guidance

Detection should focus on unexpected WordPress administrator creation, suspicious requests to public ACFE forms, and use of the _acf_post_id parameter in unauthenticated traffic. A newly created administrator is often the most reliable post-exploitation indicator because successful exploitation is intended to produce a persistent privileged account.

Review WordPress user records for accounts created during the exposure window. Correlate creation timestamps with web server, reverse proxy, CDN, WAF, PHP, and WordPress application logs. Pay particular attention to requests that precede user_register or administrator-account creation events and originate from unusual addresses, hosting providers, VPNs, or automation infrastructure.

Technical Notes

A generic web-server search can identify requests containing the vulnerable parameter:

zgrep -hEi '(_acf_post_id|acfe|acf-extended|admin-ajax\.php|wp-json)' \
  /var/log/nginx/access.log* /var/log/apache2/access.log* 2>/dev/null

This is a triage pattern, not a definitive exploit signature. _acf_post_id may appear in legitimate ACFE requests, and attackers may alter request formatting or use a route not captured by the chosen log source. Correlate matching requests with POST status codes, response sizes, source IP reputation, and subsequent user creation.

A practical SQL review for recently created administrators depends on the site’s database schema and table prefix. For a conventional WordPress installation, begin with:

SELECT ID, user_login, user_email, user_registered
FROM wp_users
WHERE user_registered >= '2026-05-28'
ORDER BY user_registered DESC;

Then inspect capabilities for those users:

SELECT u.ID, u.user_login, u.user_registered, m.meta_value
FROM wp_users AS u
JOIN wp_usermeta AS m ON m.user_id = u.ID
WHERE m.meta_key = 'wp_capabilities'
  AND m.meta_value LIKE '%administrator%';

Replace wp_ with the site’s actual table prefix. Also check WordPress security-plugin audit logs and identity systems for account-creation events. Because log field names vary by product, there is no universally reliable single SIEM query; the key events are a public form POST containing _acf_post_id, followed by creation or modification of a user with administrator capability.

Remediation Steps

All versions through and including 0.9.2.5 should be considered affected. Upgrade Advanced Custom Fields: Extended to the first vendor release that explicitly contains the CVE-2026-8809 fix. The supplied evidence confirms WordPress.org changeset 3551665, but does not establish the exact fixed plugin version. Do not report a specific fixed release until it is confirmed from the vendor’s release metadata or the WordPress.org plugin repository.

If a verified fixed release is available through the WordPress administration interface, use the normal plugin update workflow after confirming the package source and testing it in a staging environment. A command-line workflow can be used once the fixed version is known:

wp plugin update acf-extended
wp plugin list --name=acf-extended --fields=name,status,version,update

A successful update command does not prove that the installed version is fixed. Compare the resulting version with the vendor-confirmed fixed release.

Technical Notes

If no verified fixed release is available, disable the plugin or remove it after preserving configuration and checking application dependencies:

wp plugin deactivate acf-extended
# Remove only after confirming the site does not depend on the plugin:
wp plugin delete acf-extended

As an interim workaround, disable or remove public ACFE frontend forms using the Create User action. If that cannot be done immediately, require authentication and place the form behind a network control or WAF policy. These measures reduce exposure but should not replace upgrading or removing the vulnerable component.

After remediation:

  1. Review all WordPress users created or modified during the period of exposure.
  2. Remove unauthorized accounts and revoke unexpected sessions or application passwords.
  3. Rotate WordPress administrator credentials and any secrets accessible through the site.
  4. Review plugins, themes, scheduled tasks, webhooks, and modified PHP files for persistence.
  5. Examine web and WordPress logs for suspicious form submissions and administrative activity.
  6. Confirm that public registration and user-creation workflows still enforce an approved role allow-list.
  7. Monitor for newly created administrator accounts and unexpected plugin installations.

If an unauthorized administrator account is found, treat the site as potentially compromised rather than as a simple configuration issue. Preserve relevant logs and filesystem evidence before cleanup, and consider rebuilding from a known-good source if post-compromise integrity cannot be established.

Choosing a tool? Pricing and head-to-head guides

Last verified: 2026-11-17

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.