dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-5396

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

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 Fluent Forms plugin for WordPress is vulnerable to Authorization Bypass Through User-Controlled Key in all versions up to, and including, 6.1.21. This is due to the SubmissionPolicy class authorizing submission-level actions (read, modify, delete, add notes) based on a user-supplied `form_id` query parameter. This makes it possible for authenticated attackers, with Fluent Forms Manager access restricted to specific forms, to read, modify status, add notes to, and permanently delete form submissions belonging to any other form by spoofing the form_id parameter to a form they are authorized for.

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 confidence

The Fluent Forms plugin's SubmissionPolicy class authorizes submission actions (read, modify, delete, add notes) based on a user-supplied `form_id` query parameter without properly validating that the requesting user has permission for that specific form. This IDOR-style vulnerability allows authenticated attackers with limited Fluent Forms Manager access to manipulate the form_id parameter to access, modify status, add notes to, or permanently delete submissions belonging to any form on the site.

MitigationUpdate to version 6.1.22 or later when available. As an interim measure, audit user roles and permissions in Fluent Forms, and consider using a web application firewall to detect anomalous form_id parameter manipulation.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

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. Confirm Fluent Forms plugin is installed
    Navigate to WordPress admin dashboard > Plugins and verify Fluent Forms appears in the list of installed plugins
    Affected if Fluent Forms plugin is present in the WordPress installation
  2. Identify the installed Fluent Forms version
    In the Plugins list, find Fluent Forms and note the version number displayed; compare this against the affected range (versions prior to 6.1.22)
    Affected if The installed version is earlier than 6.1.22
  3. Verify the SubmissionPolicy class is present
    Check the plugin files for the presence of a SubmissionPolicy class file, typically located in the includes or classes directory of the Fluent Forms plugin
    Affected if The SubmissionPolicy class exists and handles submission actions
  4. Check for users with form Manager capabilities
    In WordPress admin, go to Users > All Users and review user roles; identify any users assigned to roles that include form Manager or submission management capabilities
    Affected if There are users with limited form Manager access to the plugin
  5. Test access to submissions via manipulated form_id parameter
    Using a browser or HTTP tool, access the submissions endpoint (typically /wp-admin/admin-ajax.php or a submissions list page) with a form_id parameter pointing to a form the current user should not have access to; observe if submissions from other forms are returned or modifiable
    Affected if A user with limited form access can view, modify, delete, or add notes to submissions from forms they do not own by manipulating the form_id parameter

The environment is affected if Fluent Forms version is earlier than 6.1.22 and users with limited form Manager permissions can access or manipulate submissions from forms outside their assigned scope by manipulating the form_id parameter.

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 6.1.22 or later when available. As an interim measure, audit user roles and permissions in Fluent Forms, and consider using a web application firewall to detect anomalous form_id parameter manipulation.

Recommended fix Moderate confidence

Latest version after 6.1.21 (check WordPress plugin repository for current stable release)

  1. Check the WordPress admin dashboard for available plugin updates under Dashboard > Updates
  2. Update Fluent Forms plugin to the latest version available in the WordPress plugin repository
  3. Alternatively, navigate to Plugins > Installed Plugins > Fluent Forms and click 'Update Now' if an update is available
  4. After updating, verify that form submission permissions are working correctly by testing access controls between forms

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5396 — 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-5396 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