FormFlow versions through 3.10.2 have an unauthenticated arbitrary file upload vulnerability rated CVSS 10 by Patchstack. The disclosure, published October 31, 2026, identifies version 3.11.0 as patched. Site owners using the plugin should check its installed version and update if it falls within the affected range.
This FormFlow vulnerability is the clearest urgent item in WordPress ecosystem news today: Patchstack lists no required privilege for exploitation and recommends updating to version 3.11.0 or later. The advisory does not describe a specific attack method or report active exploitation, so the practical response is to verify the version and apply the fix.
What the FormFlow vulnerability affects
In its October 31 advisory, Patchstack identifies the affected product as FormFlow, a WordPress plugin. Versions 3.10.2 and earlier are vulnerable; version 3.11.0 is listed as the patched release. The record assigns the issue CVE-2026-118235 and credits researcher whysocscs.
Patchstack classifies the flaw as an arbitrary file upload and gives it a CVSS severity score of 10. The advisory says an unauthenticated user can trigger the vulnerability. In general, arbitrary file upload flaws can let an attacker place files on a server; Patchstack warns that this type of issue can be used to take over a site.
The advisory does not say how many sites have FormFlow installed, whether attackers are exploiting this issue, or what file types or upload conditions are involved. Those details should not be assumed from the severity score alone. The confirmed facts are enough to make version checking the priority for site owners.
What WordPress site owners should do
Check each site that uses FormFlow and confirm the installed version. If it is 3.10.2 or earlier, update to 3.11.0 or later, the version range Patchstack lists as patched. If you manage sites for clients, include the plugin in your next update review rather than relying on a single site-wide update check.
If the plugin is no longer needed, removing it is a reasonable way to reduce the software that needs maintenance. If you cannot update immediately, contact your developer or hosting provider for help, as Patchstack advises. Its advisory does not provide a workaround that can be presented as equivalent to installing the patched release.
After updating, verify the plugin’s version in the WordPress dashboard or your usual deployment records. Keep a note of any site where the update could not be applied, then follow up until the version is confirmed. That is a straightforward response to the published disclosure without treating unreported exploitation as fact.
Why this disclosure matters
The high score and unauthenticated access make this a time-sensitive update for sites running affected versions. The key distinction is that Patchstack describes the vulnerability as severe, but does not say it is being actively exploited. Site owners can act on the published severity and fix version while keeping that distinction clear.
For teams that track WordPress ecosystem news, the immediate takeaway is specific: find FormFlow installations and ensure they run version 3.11.0 or later. Do not wait for evidence of attacks before applying a version Patchstack identifies as patched.
FormFlow vulnerability FAQ
Which FormFlow versions are affected?
Patchstack lists versions 3.10.2 and earlier as vulnerable. It identifies version 3.11.0 as patched.
Does exploiting the FormFlow flaw require an account?
No account or other privilege is required, according to Patchstack’s advisory. The finding is classified as an unauthenticated arbitrary file upload vulnerability.
Is the vulnerability being actively exploited?
Patchstack’s advisory does not report active exploitation. It rates the issue CVSS 10 and recommends updating, so site owners should check affected installations and apply version 3.11.0 or later.
Next step: Check your WordPress sites for FormFlow and update any installation running version 3.10.2 or earlier.