Flynax Bridge <= 2.2.0 - Unauthenticated Privilege Escalation via Password Update
Strategic Overview
- Status
- Patched in 2.2.1
- Affected Plugin
- Flynax Bridge
- Affected Version
<= 2.2.0- CVSS
- 9.8Critical
- Weakness type
- CWE-620 · Unverified Password Change
- CVE
CVE-2025-3603
At a glance
CVE-2025-3603 is a critical-severity Unverified Password Change vulnerability in the Flynax Bridge WordPress plugin, affecting versions <= 2.2.0. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.2.1; sites on affected versions should update now. Disclosed April 2025, reported by kr0d.
Vulnerability Overview
The Flynax Bridge plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 2.2.0. This is due to the plugin not properly validating a user's identity prior to updating their details like password. This makes it possible for unauthenticated attackers to change arbitrary user's passwords, including administrators, and leverage that to gain access to their account.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-620: Unverified Password Change
Reaching this weakness in Flynax Bridge <= 2.2.0 takes no account at all. Unverified password change means the password-update path does not require proof that the requester is the account owner.
An attacker who can reach the endpoint takes over the account outright, and the legitimate owner is locked out of it. 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
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C