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

CVE-2026-5395

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 – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 6.2.0 via the exportEntries function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Fluent Forms manager-level access and above, to bypass form-level access restrictions to access submissions from forms they are not authorized to view, export data from arbitrary database tables, and enumerate database table names via error message disclosure.

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 WordPress plugin has an Insecure Direct Object Reference (IDOR) vulnerability in the exportEntries function. Attackers with manager-level access can exploit missing validation on user-controlled keys to access submission data from unauthorized forms, export arbitrary database tables, and enumerate database table names through error messages.

MitigationUpdate to the latest version of Fluent Forms plugin (beyond 6.2.0) which should include proper validation on user-controlled keys in the exportEntries function, and review role-based access controls.

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. Verify Fluent Forms plugin is installed
    Navigate to WordPress admin > Plugins and confirm Fluent Forms plugin is listed as active, or check the plugins directory for fluentform folder
    Affected if Plugin is installed and active
  2. Check installed Fluent Forms version
    In WordPress admin, go to Plugins > Fluent Forms and view the version number, or inspect the fluentform/bootstrap.php file for the version constant
    Affected if Version is 6.2.0 or lower (vulnerable)
  3. Identify users with Fluent Forms manager access
    Go to Fluent Forms > Users & Roles or check WordPress user capabilities for fluentform_manager role
    Affected if Any untrusted or unknown user has manager-level access
  4. Audit exportEntries function accessibility
    Check if the /wp-json/fluentform/v1/entries-export endpoint is accessible to manager-level users without additional form ownership verification
    Affected if Manager-level users can export entries from forms they do not own

A user is affected if Fluent Forms version 6.2.0 or lower is installed AND there are untrusted users with manager-level access who could exploit the IDOR in the exportEntries function.

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 the latest version of Fluent Forms plugin (beyond 6.2.0) which should include proper validation on user-controlled keys in the exportEntries function, and review role-based access controls.

Recommended fix Moderate confidence

Upgrade to Fluent Forms version 6.2.1 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, navigate to Dashboard > Updates and select the Fluent Forms plugin to update
  6. 6. After updating, verify the plugin version is 6.2.1 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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 locally
dbcve dependency scanner

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