Loading vulnerability…
CVE-2026-8809 is a privilege escalation vulnerability in the Advanced Custom Fields: Extended (ACFE) plugin for WordPress affecting all versions up to and including 0.9.2.5. The flaw is caused by improper trust of the attacker-controlled _acf_post_id POST parameter in the after_validate_save_post() function, which uses that value without authentication or integrity verification to choose a cleanup path that silently discards validation errors not prefixed with acfe:. As a result, an unauthenticated attacker can suppress both the role allow-list validation error generated by acfe_field_user_roles::validate_front_value() and the administrator-role capability guard error generated by acfe_module_form_action_user::validate_action(). This bypass allows wp_insert_user() to be reached with an attacker-supplied administrator role value, leading to creation of a new administrator-level account.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains a single Python proof-of-concept exploit and a README describing CVE-2026-8809 affecting the WordPress plugin Advanced Custom Fields: Extended. The script is a standalone web exploit, not tied to a major framework. Its workflow is: fetch a supplied target page, search the HTML/JS for an _acf_post_id value using several regex patterns, fall back to a random numeric post ID if none is found, generate random credentials for a new user, build a crafted POST body with acf[role]=administrator and action=acfe/form/submit, then submit the payload back to the provided target URL. The intended capability is unauthenticated privilege escalation via front-end form abuse, resulting in creation of a new administrator account. The code uses requests.Session with a custom User-Agent and performs only basic success checking by looking for HTTP 200 and generic success strings. Repository structure is minimal: one exploit file (CVE-2026-8809.py) and one explanatory README. Notable limitations: the exploit assumes the vulnerable form posts to the same URL, hardcodes acf[form_id]=1, and does not dynamically discover the actual form action or all required hidden fields, so it is best classified as an operational PoC rather than a fully weaponized exploit.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.