CVE-2026-6226
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Frontend Admin by DynamiApps plugin for WordPress is vulnerable to unauthenticated privilege escalation in versions up to and including 3.29.2. This is due to insecure form submission handling that accepts arbitrary form definitions from user input instead of securely loading them from the backend. When $_POST['_acf_form'] is an array (rather than a form ID), the validate_form() function bypasses database lookup and directly processes the attacker-controlled structure. The create_record() function preserves attacker-supplied record data if present, and the user action's run() function falls back to attacker-controlled field definitions from $form['fields'] when legitimate fields cannot be found. The role field's pre_update_value() validation reads $field['role_options'] from this attacker-controlled definition, allowing an attacker to specify ['administrator'] as an allowed role and bypass the security check. This makes it possible for unauthenticated attackers to create administrator accounts by injecting a custom form configuration with a spoofed role field.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Frontend Admin WordPress plugin versions up to 3.29.2 has an unauthenticated privilege escalation vulnerability. Attackers can inject arbitrary form definitions via the $_POST['_acf_form'] parameter when it's an array rather than a valid form ID. The plugin's validate_form(), create_record(), and user action's run() functions process this attacker-controlled structure, allowing the role field's pre_update_value() to accept ['administrator'] as a role option. This enables unauthenticated attackers to create administrator accounts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Frontend Admin plugin is installedCheck the WordPress plugins directory for the 'frontend-admin' folder, or query the wp_plugins database table for plugin slug containing 'frontend-admin'Affected if Plugin folder exists in /wp-content/plugins/ or plugin row exists in wp_plugins table
-
Check installed plugin versionIf plugin is installed, read the main plugin file header (usually index.php or frontend-admin.php) to find the 'Version:' comment, or query wp_options for option_name='active_plugins' and check plugin file headersAffected if Version is 3.29.2 or lower, or version cannot be determined (unpatched)
-
Confirm plugin is active on the siteCheck if the plugin appears in the array stored in wp_options where option_name = 'active_plugins', or attempt to access a page using Frontend Admin shortcodesAffected if Plugin is active and accessible to unauthenticated users
-
Verify ACF form submission endpoint is accessibleTest if POST requests to any WordPress page can accept the '_acf_form' parameter - attempt a test request (in a non-production/test environment) sending '_acf_form' as an array to see if the application accepts itAffected if The '_acf_form' parameter is accepted as an array and processed without validation
If the Frontend Admin plugin version 3.29.2 or lower is installed and active, the site is vulnerable to unauthenticated privilege escalation via the '_acf_form' parameter handling.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the Frontend Admin by DynamiApps plugin to version 3.29.3 or later. If immediate updating is not possible, consider disabling the plugin or implementing web application firewall rules to block suspicious $_POST['_acf_form'] array submissions.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6226 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6226 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data