Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder 5.1.16 - 6.1.1 - Authenticated (Subscriber+) PHP Object Injection To Arbitrary File Read
Strategic Overview
- Status
- Patched in 6.1.2
- Affected Plugin
- Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder
- Affected Version
5.1.16 – 6.1.1- CVSS
- 6.5Medium
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE-2025-9260
At a glance
CVE-2025-9260 is a medium-severity Deserialization of Untrusted Data vulnerability in the Fluent Forms WordPress plugin, affecting versions 5.1.16 – 6.1.1. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 6.1.2; sites on affected versions should update now. Disclosed September 2025, reported by Webbernaut.
Vulnerability Overview
The Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder plugin for WordPress is vulnerable to PHP Object Injection in versions 5.1.16 to 6.1.1 via deserialization of untrusted input in the parseUserProperties function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject a PHP Object. The additional presence of a POP chain allows attackers to read arbitrary files. If allow_url_include is enabled on the server, remote code execution is possible. While the vendor patched this issue in version 6.1.0, the patch caused a fatal error in the vulnerable code, due to a missing class import, so we consider 6.1.2 to be the most complete and best patched version.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-502: Deserialization of Untrusted Data
Reaching this weakness in Fluent Forms 5.1.16 – 6.1.1 takes an account at Subscriber level or above. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.
A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For Fluent Forms the fix is 6.1.2: builds 5.1.16 – 6.1.1 are affected, anything from 6.1.2 onward is not.
Remediation
Update to version 6.1.2, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Fluent Forms 6.1.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder
- 9.8CVE-2024-2771: Contact Form Plugin… Settings Update and Limited
CVE-2024-2771 - 8.8CVE-2021-34620: WP Fluent Forms < 3.6.67 Stored Cross-Site Scripting
CVE-2021-34620 - 8.3CVE-2022-3463: Contact Form Plugin by FluentForm CSV Injection
CVE-2022-3463 - 8.2CVE-2026-5395: Fluent Forms <= 6.2.0 Authorization Bypass
CVE-2026-5395 - 8.2CVE-2026-5396: Fluent Forms <= 6.1.21 Authorization Bypass
CVE-2026-5396 - 7.5CVE-2024-2782: Contact Form Plugin… Setting Manipulation
CVE-2024-2782 - 7.2CVE-2026-18146: Fluent Forms <= 6.2.11 Stored Cross-Site Scripting
CVE-2026-18146 - 7.2CVE-2026-16655: Fluent Forms <= 6.2.7 Stored Cross-Site Scripting
CVE-2026-16655
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C