CVE-2025-4177: The Flynax Bridge plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability

Q: How do I fix CVE-2025-4177?

flynax bridge: upgrade to newer than 2.2.0. Exact commands for each OS are on this page.

Q: Is CVE-2025-4177 being exploited?

CVE-2025-4177 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-4177 affect?

CVE-2025-4177 affects flynax bridge. Severity is medium (CVSS 5.3). The Flynax Bridge plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the deleteUser() function in all versions up to, and including, 2.2.0. This makes it possible for unauthenticated attacke

Q: How urgent is CVE-2025-4177?

Priority 31/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.3REMOTEUPGRADE

CVE-2025-4177 is a medium-severity flaw (CVSS 5.3) affecting flynax bridge. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Flynax Bridge plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the deleteUser() function in all versions up to, and including, 2.2.0. This makes it possible for unauthenticated attackers to delete arbitrary users.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 70%)
CISA exploited list	No
Weakness	CWE-862
Published	2025-05-02
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: flynax

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-05-02 03:15 UTCPublished CVE record published
2026-06-17 09:32 UTCUpdated Record last modified

flynax flynax bridge UPGRADE

Affected: <= 2.2.0

Fixed in: newer than 2.2.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy flynax-bridge || rpm -q flynax-bridge || flynax-bridge --version

2. UPGRADE to newer than 2.2.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade flynax-bridge

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade flynax-bridge

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-4177?

flynax bridge: upgrade to newer than 2.2.0. Exact commands for each OS are on this page.

Is CVE-2025-4177 being exploited?

CVE-2025-4177 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-4177 affect?

CVE-2025-4177 affects flynax bridge. Severity is medium (CVSS 5.3). The Flynax Bridge plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the deleteUser() function in all versions up to, and including, 2.2.0. This makes it possible for unauthenticated attacke

How urgent is CVE-2025-4177?

Priority 31/100. Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2025-4179 HIGH 7.3 UPGRADE The Flynax Bridge plugin for WordPress is vulnerable to limited Privilege Escalation due to a missing capabili
CVE-2025-3604 CRITICAL 9.8 UPGRADE The Flynax Bridge plugin for WordPress is vulnerable to privilege escalation via account takeover in all versi
CVE-2025-3603 CRITICAL 9.8 UPGRADE The Flynax Bridge plugin for WordPress is vulnerable to privilege escalation via account takeover in all versi

References

← Back to latest CVEs