dbcve.org
Front End UsersWordPress extension · Etoilewebdesign

CVE-2025-47580

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-15
Fix available
A fix is available. Upgrade to after 3.2.32 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Missing authorization vulnerability in Rustaurius Front End Users plugin allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to user data or administrative functions intended only for permitted users.

MitigationUpdate to the latest version of Front End Users plugin which should contain proper authorization controls, or implement explicit authorization checks on all sensitive endpoints/functions within the plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Front End UsersWordPress extension
Affected:<= 3.2.32

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Front End Users plugin installation
    Check your WordPress site's wp-content/plugins/ directory for a folder named 'front-end-users' or similar variant of the Etoilewebdesign Front End Users plugin
    Affected if The plugin folder exists in the plugins directory
  2. Verify the installed plugin version
    Open the main plugin PHP file (usually the primary .php file in the plugin folder) and locate the version comment in the plugin header (e.g., 'Version: x.x.x')
    Affected if The version listed is 3.2.32 or lower (any version <= 3.2.32)
  3. Confirm the plugin is active
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or query the wp_options table for the active_plugins option to check if Front End Users is enabled
    Affected if The plugin shows as Active in WordPress
  4. Inspect access control configuration
    Review the plugin settings in WordPress admin under the plugin's settings page, looking for any security level, user role, or access permission configuration options that may be incorrectly set
    Affected if Security level or role access settings allow access to sensitive functions for unauthorized user roles

Your environment is affected if the Front End Users plugin by Etoilewebdesign is installed, active, and running version 3.2.32 or lower, with potentially misconfigured access control settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.2.32
Interim mitigation

Update to the latest version of Front End Users plugin which should contain proper authorization controls, or implement explicit authorization checks on all sensitive endpoints/functions within the plugin.

Recommended fix Moderate confidence

Version 3.2.36 or later

  1. 1. Back up your WordPress site database and files.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Find the 'Front End Users' plugin by Rustaurius.
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version.
  5. 5. After updating, verify the plugin version is 3.2.36 or higher.
  6. 6. Test user registration, login, and access control functionality to ensure the authorization fix works correctly.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Front End Users Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47580 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-47580 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data