Skip to main content

Fluent Forms EUVDEUVD-2026-96226

| CVE-2026-15178 MEDIUM
Missing Authorization (CWE-862)
2026-10-10 Wordfence GHSA-pmcp-c5j9-q942
5.4
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as Custom-level WordPress user
  2. Exploit
    Send request to unprotected Fluent Forms Acl action
  3. Execution
    Bypass missing authorization check
  4. Impact
    Read, alter, or delete submissions and change plugin settings

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated WordPress account with Custom-level capabilities or above on a site running Fluent Forms ≤ 6.2.5; the vulnerable actions are reachable over the network with no user interaction and low complexity once such an account is held. The key limiting factor is the privilege prerequisite (PR:L): sites that only grant Administrator/Editor roles to trusted staff have little exposure, while multi-user deployments (membership, e-commerce, LMS, agency, or guest-contributor sites) that provision lower or custom roles are directly at risk. No special non-default plugin configuration is named as a prerequisite beyond the plugin being installed and active and the attacker possessing a qualifying role.

Impact

This is a moderate-severity authorization flaw (CVSS 5.4) that in practice sits below the top-priority tier. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N indicates network-reachable, low-complexity exploitation but explicitly requires authentication (PR:L) - the attacker must already hold a Custom-level WordPress account or higher, which is a meaningful barrier on sites that do not hand out elevated roles freely. Impact is constrained to C:L/I:L/A:N: partial disclosure of private submissions and unauthorized modification/deletion of submission data and plugin settings, with no direct availability impact to the host. No EPSS score, KEV listing, or public POC was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The practical risk is therefore elevated mainly on multi-user sites (membership, e-commerce, LMS, or agency installs) where low-privilege authenticated accounts are common; on single-admin sites the required privilege sharply limits real-world exposure. Note one tension worth verifying: the input tags label this 'Authentication Bypass,' but the description and CWE-862 (Missing Authorization) make clear it is an authorization (privilege) bypass by an already-authenticated user - not an authentication bypass.

Exploit ScenarioDerived

On a WordPress site that assigns Custom-level or higher accounts to non-administrators (e.g., a membership or multi-contributor site), an attacker logs in with their low-privilege account and sends requests directly to Fluent Forms actions that fail to check authorization. With low attack complexity and no user interaction, they read other users' private form submissions, flip submission statuses, permanently delete entries, and tamper with global plugin settings. No public exploit code was identified at time of analysis, but the flaw is trivially reachable once a qualifying account is held.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 10, 2026

Fluent Forms for WordPress (all versions up to and including 6.2.5) fails to verify that a user is authorized before performing several form-management actions, allowing an authenticated attacker holding Custom-level access or above to read private form submissions, change submission statuses, permanently delete submissions, and modify global plugin settings. The flaw is a missing-authorization issue (CWE-862) reachable over the network with low complexity and no user interaction once a qualifying account exists, and the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N, score 5.4) reflects limited confidentiality and integrity impact with no availability impact. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing); the practical exposure is concentrated in multi-user sites that provision low-privilege or custom roles.

RemediationAI

Upstream fix available (PR/commit); released patched version not independently confirmed - the vendor's corrective change is the ACL modification in Fluent Forms changeset 3602478 (app/Modules/Acl/Acl.php), so administrators should update the plugin to the latest WordPress.org release and verify the installed version is greater than 6.2.5 rather than assuming any specific tagged patch number from the available data. Where an immediate upgrade is not possible, restrict the attack surface by removing or downgrading Custom-level and other low-privilege roles that the plugin honors (auditing each role's capabilities in Users → Roles and confirming no untrusted account can reach Fluent Forms entry-management screens), accepting the trade-off that legitimate contributors who relied on those roles lose access to submissions and settings; alternatively deactivate Fluent Forms entirely until patched, which stops the exposure at the cost of taking all live forms offline. Additional compensating actions with their own costs include tightening the site's role provisioning so that only Administrators and Editors handle form data (break-glass for membership, LMS, or e-commerce sites that intentionally grant lower roles), exporting and reviewing the wp_fluentform_submissions and related tables for unauthorized reads or deletions before restoring from backup, and monitoring plugin option changes for tampering with global settings. Because exploitation requires only a valid low-privileged session, credential hygiene, forced password resets for Custom-level accounts, and review of recently created accounts are worthwhile supplemental controls. Refer to the vendor advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/10f5eef7-ea2f-44ee-8907-da53ced19180?source=cve for the authoritative fix guidance.

Affected VersionsENISA

Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder 0 ≤6.2.5

Affected Packages

euvd fluent_forms_customizable_contact_forms_survey_quiz_conversational_form_builder no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability sits in Fluent Forms' access-control layer, which in the upstream tree is implemented by the Acl module (app/Modules/Acl/Acl.php, touched by the referenced changeset). CWE-862 (Missing Authorization) means the affected request handlers - the AJAX/REST endpoints that list and manipulate form entries and that write global plugin options - execute their business logic without first calling a capability or permission check such as current_user_can() or an equivalent ACL assertion. Because WordPress capability checks are the only barrier between a low-privileged logged-in user and these entry-management routines, any role that the plugin treats as 'Custom-level' or higher can reach them. The CPE cpe:2.3:a:wpmanageninja:fluent_forms_-_customizable_contact_forms,_survey,_quiz,_&_conversational_form_builder:*:*:*:*:*:*:*:* confirms the affected component is the wpmanageninja Fluent Forms plugin distributed through WordPress.org, and the CPE version wildcard is consistent with the vendor statement that all versions through 6.2.5 are affected. This is a privilege-escalation-adjacent data-access and configuration-tampering issue rather than a code-execution or injection flaw; the underlying technology is the WordPress role/capability model combined with the plugin's own ACL abstraction.

Know when Fluent Forms Customizable Contact Forms Survey Quiz Conversational Form Builder gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 5.4 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
vuln.today AI 5.4 MEDIUM

Network-reachable action with low complexity and no UI, but requires an authenticated Custom-level account (PR:L); partial data read and modify/delete yield C:L/I:L, no host availability impact (A:N).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

The Fluent Forms plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 6.2.5. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with Custom-level access and above, to read private form submissions, change submission statuses, permanently delete submissions, and modify global plugin settings.

Threat Intelligence Overview

EPSS Score
0.2%
Top 96% exploitable
Prevalence
High
Fluent Forms is a widely deployed WordPress form plugin with large install base
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
High
Technical Impact
Partial

Priority Score

27
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +27
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy