dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-14736

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-09
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 Admin by DynamiApps plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 3.28.29. This is due to insufficient validation of user-supplied role values in the 'validate_value', 'pre_update_value', and 'get_fields_display' functions. This makes it possible for unauthenticated attackers to register as administrators and gain complete control of the site, granted they can access a user registration form containing a Role field.

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 Admin plugin fails to validate user-supplied role values in three functions (validate_value, pre_update_value, and get_fields_display), allowing unauthenticated attackers to specify 'administrator' as their role during user registration. This grants them full admin privileges and complete control over the WordPress site.

MitigationUpdate the plugin to version 3.28.30 or later. Until patched, disable any public user registration forms containing Role fields or restrict access to prevent unauthenticated access.

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 Admin plugin is installed
    Log into WordPress admin, go to Plugins > Installed Plugins, and locate 'Frontend Admin' in the list. Alternatively, check the plugins directory via file system or use: wp plugin list --name='frontend-admin'
    Affected if The plugin is installed and active on the WordPress site
  2. Check installed plugin version
    In WordPress adminPlugins page, click on the plugin name to view details and note the version number. Or use: wp plugin get frontend-admin --format=json
    Affected if Version is lower than 3.28.30 (vulnerable); version 3.28.30 or later contains the fix
  3. Identify frontend registration forms with Role fields
    Review pages/posts containing [frontend_admin] shortcodes or custom registration forms. Check formbuilder settings for any form element labeled 'Role', 'User Role', or 'Select Role' that allows the user to choose their role during registration.
    Affected if A registration form exists that includes a Role selection field accessible to users
  4. Confirm public access to vulnerable forms
    View the registration form on the frontend while logged out (incognito browser). Verify if unauthenticated visitors can access and submit the form. Check that the form is not restricted to logged-in users only.
    Affected if The registration form with Role field is accessible to unauthenticated visitors without login requirements
  5. Check WordPress user registration settings
    Go to WordPress Settings > General and verify if 'Anyone can register' is enabled, and that the default role is set to allow user creation.
    Affected if Site allows public user registration, which enables the attack vector for assigning administrator privileges

The site is affected if Frontend Admin plugin version is below 3.28.30 AND a registration form with a Role field is publicly accessible to unauthenticated users.

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 plugin to version 3.28.30 or later. Until patched, disable any public user registration forms containing Role fields or restrict access to prevent unauthenticated access.

Recommended fix High confidence

Frontend Admin by DynamiApps version 3.28.30 or later

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to Plugins > All Plugins in the WordPress admin dashboard
  3. Find 'Frontend Admin by DynamiApps' in the plugin list
  4. Click 'Update now' to install the latest version, or manually upload version 3.28.30 or later if auto-update is unavailable
  5. After updating, verify the plugin version shows 3.28.30 or higher in the Plugins list
  6. Review any user registration forms on the site to ensure they do not expose a Role field to unauthenticated users, or restrict role selection to lower-privileged roles only
  7. Verify existing administrator accounts have not been modified by checking Users > All Users

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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