CVE-2025-13722
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 Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 6.1.7. This is due to missing capability checks on the `fluentform_ai_create_form` AJAX action. This makes it possible for authenticated attackers, with Subscriber-level access and above, to create arbitrary forms via the publicly exposed AI builder.
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 Fluent Forms WordPress plugin has a missing authorization vulnerability in the AI form builder AJAX endpoint. The `fluentform_ai_create_form` action lacks capability verification, allowing any authenticated user with Subscriber-level access or higher to create arbitrary forms via the publicly accessible AI builder. This is a classic broken access control (BAC) vulnerability where the function assumes caller authorization without verifying it.
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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Fluent Forms versionIn WordPress admin, go to Plugins > Installed Plugins > Fluent Forms and look at the Version number, or check the version in the plugin header file fluent-form.phpAffected if Version is earlier than 6.1.8 (the patched release)
-
Verify AI builder endpoint is accessibleCheck if the AJAX action fluentform_ai_create_form is registered and publicly accessible - this can be confirmed by examining the plugin's admin-ajax.php registration or testing if a subscriber-level user can access the endpointAffected if The endpoint responds to requests from authenticated users with Subscriber role or higher without returning a capability error (403/401)
-
Confirm user role permissionsReview WordPress user roles and confirm that users with Subscriber role exist and have access to the WordPress dashboard/ajax functionalityAffected if Any user with Subscriber role or higher can make authenticated requests to the affected endpoint
You are affected if Fluent Forms version is below 6.1.8 and the AI builder endpoint is accessible to authenticated users with Subscriber-level access or higher.
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.
dbcve · scopedUpdate to version 6.1.8 or later which adds proper capability checks. Until patched, restrict access to the affected AJAX endpoint via WAF or disable the AI builder feature for non-administrative users.
Fluent Forms version 6.1.8 or latest stable release
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate Fluent Forms plugin
- Check if an update is available and update to version 6.1.8 or later
- Alternatively, download the latest version from wordpress.org/plugins/fluentform/ and upload via Plugins > Add New > Upload Plugin
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13722 — 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-2025-13722 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