Flynax Bridge <= 2.2.0 - Unauthenticated Limited Privilege Escalation
Strategic Overview
- Status
- Patched in 2.2.1
- Affected Plugin
- Flynax Bridge
- Affected Version
<= 2.2.0- CVSS
- 7.3High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-4179
At a glance
CVE-2025-4179 is a high-severity Missing Authorization vulnerability in the Flynax Bridge WordPress plugin, affecting versions <= 2.2.0. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.2.1; sites on affected versions should update now. Disclosed May 2025, reported by kr0d.
Vulnerability Overview
The Flynax Bridge plugin for WordPress is vulnerable to limited Privilege Escalation due to a missing capability check on the registerUser() function in all versions up to, and including, 2.2.0. This makes it possible for unauthenticated attackers to register new user accounts as authors.
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 privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Flynax Bridge <= 2.2.0 carries this weakness at registerUser(), and reaching it takes no account at all. 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 Flynax Bridge the fix is 2.2.1: builds <= 2.2.0 are affected, anything from 2.2.1 onward is not.
Remediation
Update to version 2.2.1, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Flynax Bridge 2.2.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Flynax Bridge
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C