CVE-2025-47580: Missing Authorization vulnerability in Rustaurius Front End Users front-end-only-users allows Exploiting Incor

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

front end users: upgrade to newer than 3.2.32. Exact commands for each OS are on this page.

Q: Is CVE-2025-47580 being exploited?

CVE-2025-47580 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-47580 affect?

CVE-2025-47580 affects front end users. Severity is medium (CVSS 5.4). Missing Authorization vulnerability in Rustaurius Front End Users front-end-only-users allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Front End Users: from n/a through <= 3.2.35.

Q: How urgent is CVE-2025-47580?

Priority 24/100. No elevated risk signals yet.

Routine

MEDIUM 5.4UPGRADE

CVE-2025-47580 is a medium-severity flaw (CVSS 5.4) affecting front end users. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Missing Authorization vulnerability in Rustaurius Front End Users front-end-only-users allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Front End Users: from n/a through <= 3.2.35.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

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

Publisher (CNA): Patchstack · Vendor: etoilewebdesign

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

Am I affected?

Timeline

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

etoilewebdesign front end users UPGRADE

Affected: <= 3.2.32

Fixed in: newer than 3.2.32

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy front-end-users || rpm -q front-end-users || front-end-users --version

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

sudo apt update && sudo apt install --only-upgrade front-end-users

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade front-end-users

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-47580?

front end users: upgrade to newer than 3.2.32. Exact commands for each OS are on this page.

Is CVE-2025-47580 being exploited?

CVE-2025-47580 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-47580 affect?

CVE-2025-47580 affects front end users. Severity is medium (CVSS 5.4). Missing Authorization vulnerability in Rustaurius Front End Users front-end-only-users allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Front End Users: from n/a through <= 3.2.35.

How urgent is CVE-2025-47580?

Priority 24/100. No elevated risk signals yet.

Related CVEs

CVE-2025-2005 CRITICAL 9.8 UPGRADE The Front End Users plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type vali
CVE-2025-26877 MEDIUM 6.5 UPGRADE Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Rustauri
CVE-2024-7607 HIGH 8.8 UPGRADE The Front End Users plugin for WordPress is vulnerable to time-based SQL Injection via the ‘order’ parameter i
CVE-2024-7606 MEDIUM 6.4 UPGRADE The Front End Users plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'user-s
CVE-2024-13569 HIGH 7.1 UPGRADE The Front End Users WordPress plugin through 3.2.32 does not sanitise and escape a parameter before outputting

References

← Back to latest CVEs