dbcve.org
VulnerabilityAwaiting classification

CVE-2026-11794

HIGH · 8.1 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 weeks old

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 · unedited
The Advanced Form Integration — Connect Forms to 200+ Apps WordPress plugin before 2.1.1 does not restrict the WordPress role assigned when it creates a user from a public form submission, allowing unauthenticated visitors to create an administrator account when an active integration maps the user role to a public form field. This requires a specific, non-default multi-Advanced Form Integration — Connect Forms to 200+ Apps WordPress plugin before 2.1.1 configuration.

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 · moderate confidence

The Advanced Form Integration WordPress plugin before 2.1.1 allows unauthenticated users to create WordPress accounts via public form submissions. When an integration is configured to map user roles from a form field, attackers can specify 'administrator' as the role value to gain full admin access. This is a privilege escalation vulnerability requiring a non-default configuration where role mapping is enabled.

MitigationUpdate to version 2.1.1 or later, which restricts role assignment. Additionally, avoid mapping user roles directly to public form fields without strict allowlist validation, and audit existing integrations for this configuration.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the Advanced Form Integration plugin version
    Check the installed plugin version via WordPress admin under Plugins > Installed Plugins, or inspect the plugin's main PHP file header for the 'Version' field, or use 'wp plugin list' if WP-CLI is available. Compare the version number to the affected range (before 2.1.1).
    Affected if The installed version is earlier than 2.1.1.
  2. Identify integrations with role mapping enabled
    Access the plugin settings in WordPress admin. Navigate to Advanced Form Integration > Integrations (or similar). For each integration, locate the role mapping configuration section. Check whether a field is mapped to assign user roles based on form input.
    Affected if At least one integration has role mapping configured to assign roles from a form field.
  3. Inspect the role mapping field configuration
    In the integration settings, examine the specific field mapped to user roles. Determine whether the configuration accepts arbitrary role values from the form submission without a restricted allowlist.
    Affected if The role mapping accepts any role value from the form field, including 'administrator', without strict allowlist validation.
  4. Confirm the integration is exposed to public form submissions
    Verify that the integration is connected to a form that is accessible to unauthenticated (public) visitors. Check the form's visibility settings or confirm the form is embedded on a public-facing page without authentication requirements.
    Affected if The mapped form is publicly accessible without requiring login, allowing unauthenticated submissions.

A user is affected if the plugin version is before 2.1.1 AND an integration is configured to map user roles directly from a public form's input field without restrictive allowlist validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 2.1.1 or later, which restricts role assignment. Additionally, avoid mapping user roles directly to public form fields without strict allowlist validation, and audit existing integrations for this configuration.

Recommended fix High confidence

2.1.1

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Advanced Form Integration — Connect Forms to 200+ Apps' plugin
  4. Click 'Update now' if an update is available, or manually update to version 2.1.1
  5. Verify the plugin is running version 2.1.1 or later after updating

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11794 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11794 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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