dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-7802

HIGH · 8.8 CVSS v3.1 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 authorization bypass in all versions up to, and including, 3.29.2. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to overwrite an administrator's user_pass, user_email, first_name, last_name, and other profile fields by supplying an arbitrary ?user_id= value, enabling full administrator account takeover via direct password replacement or email-redirect password reset. Exploitation requires the targeted Edit-User form to have its 'Roles' configuration setting left empty; when a non-empty roles list is configured, load_data() sets the user ID to 'none' for users whose roles fall outside the allowed list, preventing administrators from being targeted through that form.

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 for WordPress versions up to 3.29.2 fails to properly validate user authorization in its Edit-User form, allowing authenticated attackers with subscriber-level access to supply an arbitrary user_id parameter and overwrite sensitive administrator profile fields including user_pass, user_email, and names. This enables full administrator account takeover through direct password replacement or email-redirect password reset when the form's 'Roles' configuration setting is left empty.

MitigationUpdate the Frontend Admin plugin to version 3.30 or later, or alternatively ensure the Edit-User form's 'Roles' configuration setting is NOT left empty (configured with at least one role).

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Frontend Admin' in the list. Note the version number displayed under the plugin name.
    Affected if The plugin is installed and the version is 3.29.2 or lower
  2. Confirm WordPress user roles exist
    Go to Users > Users in WordPress admin. Verify that subscriber-level or low-privilege user accounts exist on the site.
    Affected if Any subscriber-level or lower-privileged user accounts exist on the site
  3. Check Edit-User form Roles configuration
    In WordPress admin, navigate to the Frontend Admin settings. Locate any 'Edit-User' form configurations. Examine the Roles dropdown or setting and determine if it is empty (no roles selected) or left at default allowing all roles.
    Affected if The Edit-User form has an empty or unrestricted Roles setting that allows subscriber-level users to access the form
  4. Verify subscriber users can access edit user forms
    Log in as a subscriber-level user and attempt to access any user profile edit functionality provided by Frontend Admin. Check if the form loads and accepts a user_id parameter.
    Affected if Subscriber users can access the user edit form and supply arbitrary user IDs

You are affected if Frontend Admin plugin version 3.29.2 or lower is installed, the Edit-User form Roles setting is empty or unrestricted, and any subscriber-level user accounts exist on the site who could exploit the missing authorization check.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Frontend Admin plugin to version 3.30 or later, or alternatively ensure the Edit-User form's 'Roles' configuration setting is NOT left empty (configured with at least one role).

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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