dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-5069

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 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 Fluent Forms plugin for WordPress is vulnerable to incorrect authorization via the 'subscription_id' parameter in versions up to, and including, 6.2.1. This is due to insufficient ownership authorization checks in the payment cancellation AJAX flow. This makes it possible for authenticated attackers, with subscriber-level access and above, to submit cancellation requests for other users' subscriptions.

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 for WordPress fails to validate that the authenticated user owns the subscription referenced by the 'subscription_id' parameter in the payment cancellation AJAX handler. This allows any authenticated user with subscriber-level access to cancel arbitrary subscriptions by manipulating this parameter.

MitigationUpgrade Fluent Forms to version 6.2.2 or later, which should implement proper ownership verification ensuring the requesting user owns the subscription before processing cancellation.

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
None
Integrity
Low
Availability
Low

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

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
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Fluent Forms' or check wp-content/plugins/fluentform directory exists
    Affected if Plugin is installed and active
  2. Check installed Fluent Forms version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number next to Fluent Forms, or check the plugin header in wp-content/plugins/fluentform/fluentform.php for 'Version:'
    Affected if Version is lower than 6.2.2 (the fixed version)
  3. Identify user roles with access to the site
    Go to WordPress Users > Roles and check if subscriber-level or low-privilege roles exist and can access the dashboard, or query wp_usermeta for users with wp_capabilities showing subscriber-level access
    Affected if Any authenticated user with subscriber-level or higher access exists
  4. Verify AJAX payment cancellation endpoint is accessible
    Check if the fluenform_payment_cancel AJAX action is registered by searching plugin files for 'wp_ajax_fluentform_payment_cancel' or test if a subscriber-level user can access the admin-ajax.php?action=fluentform_payment_cancel endpoint
    Affected if The AJAX handler is exposed and accessible to authenticated users without ownership verification

Your environment is affected if Fluent Forms is installed with a version lower than 6.2.2 and any authenticated subscriber-level user can access the payment cancellation AJAX handler without the plugin verifying subscription ownership.

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

Upgrade Fluent Forms to version 6.2.2 or later, which should implement proper ownership verification ensuring the requesting user owns the subscription before processing cancellation.

Recommended fix Moderate confidence

Latest stable version of Fluent Forms (beyond 6.2.1)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate Fluent Forms plugin
  4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org/plugins/fluentform and upload via Plugins > Add New > Upload Plugin
  5. Verify the update to a version higher than 6.2.1 is applied
  6. Test that the payment cancellation flow still works for legitimate users

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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