dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2025-4104

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The Frontend Dashboard plugin for WordPress is vulnerable to Privilege Escalation due to a missing capability check on the fed_wp_ajax_fed_login_form_post() function in versions 1.0 to 2.2.6. This makes it possible for unauthenticated attackers to reset the administrator’s email and password, and elevate their privileges to that of an administrator.

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 · high confidence

The Frontend Dashboard WordPress plugin versions 1.0 to 2.2.6 lacks a capability check on the fed_wp_ajax_fed_login_form_post() AJAX function. This allows unauthenticated attackers to reset the administrator's email and password, effectively granting them administrator-level access to the WordPress site.

MitigationUpdate the Frontend Dashboard plugin to version 2.2.7 or later which includes proper capability validation. If immediate update is not possible, disable the plugin or restrict AJAX endpoint access at the web server level.

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

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. Verify Frontend Dashboard plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Frontend Dashboard' in the installed plugins list, or check the /wp-content/plugins/ directory for the frontend-dashboard folder
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin > Plugins, click on the Frontend Dashboard plugin to view its version, or read the main plugin file (usually frontend-dashboard.php) and look for the 'Version' header comment
    Affected if Version is 1.0 through 2.2.6 (inclusive)
  3. Confirm the vulnerable AJAX function exists
    Locate the plugin files in /wp-content/plugins/frontend-dashboard/ and search for the function 'fed_wp_ajax_fed_login_form_post' within the PHP files, particularly in ajax-related files
    Affected if The function fed_wp_ajax_fed_login_form_post() is found in the plugin code
  4. Test AJAX endpoint accessibility
    Send a POST request to /wp-admin/admin-ajax.php with action=fed_wp_ajax_fed_login_form_post (no authentication required) using curl or similar tool, and observe if the server accepts and processes the request
    Affected if The endpoint responds without requiring authentication or capability validation

If Frontend Dashboard plugin versions 1.0-2.2.6 are installed and the fed_wp_ajax_fed_login_form_post AJAX endpoint is accessible without authentication, the environment is affected by CVE-2025-4104.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Frontend Dashboard plugin to version 2.2.7 or later which includes proper capability validation. If immediate update is not possible, disable the plugin or restrict AJAX endpoint access at the web server level.

Recommended fix High confidence

Version 2.2.7 or later of the Frontend Dashboard plugin for WordPress

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Frontend Dashboard plugin
  4. Check the current version is 2.2.6 or lower
  5. Click 'Update Now' to upgrade to the latest version, or manually update to version 2.2.7 or later
  6. Verify the update was successful and the plugin is functioning correctly

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4104 — 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-4104 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