Flow-Flow Social Feed Stream 3.0.0 - 4.7.5 - Missing Authorization to Authenticated (Subscriber+) Stored Cross-Site Scripting via flow_flow_social_auth AJAX action
Strategic Overview
- Status
- Patched in 5.0.1
- Affected Plugin
- Flow-Flow Social Streams
- Affected Version
3.0.0 – 4.7.5- CVSS
- 6.4Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-13866
At a glance
CVE-2025-13866 is a medium-severity Missing Authorization vulnerability in the Flow-Flow Social Streams WordPress plugin, affecting versions 3.0.0 – 4.7.5. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.0.1; sites on affected versions should update now. Disclosed December 2025, reported by kr0d.
Vulnerability Overview
The Flow-Flow Social Feed Stream plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the flow_flow_social_auth AJAX action in versions 3.0.0 to 4.7.5. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify plugin settings and store arbitrary JavaScript that executes whenever the plugin settings page is viewed.
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.
CWE-862: Missing Authorization
Reaching this weakness in Flow-Flow Social Streams 3.0.0 – 4.7.5 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Flow-Flow Social Streams the fix is 5.0.1: builds 3.0.0 – 4.7.5 are affected, anything from 5.0.1 onward is not.
Remediation
Update to version 5.0.1, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Flow-Flow Social Streams 5.0.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Flow-Flow Social Streams
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C