dbcve.org
VulnerabilityAwaiting classification

CVE-2026-12083

HIGH · 8.1 CVSS v3.1 Published 2026-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 7 weeks old

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 Admin and Site Enhancements (ASE) WordPress plugin before 8.8.4, admin-site-enhancements-pro WordPress plugin before 8.8.4 does not perform authentication, authorization, or nonce checks on a role-restoration request handler, allowing unauthenticated attackers to restore a previously demoted administrator account back to the administrator role. This is an incomplete fix of CVE-2024-43333 / CVE-2025-24648, which closed the issue for only one of the demotion paths the WordPress role API exposes.

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 ASE WordPress plugin before 8.8.4 has an incomplete fix for a previous authentication bypass vulnerability (CVE-2024-43333/CVE-2025-24648). The role-restoration request handler lacks authentication, authorization, and nonce checks, allowing unauthenticated attackers to restore demoted administrator accounts to full admin privileges by exploiting a different demotion path in the WordPress role API that the prior fixes did not address.

MitigationUpdate Admin and Site Enhancements (ASE) plugin to version 8.8.4 or later to include the complete fix for all WordPress role API demotion paths.

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

CVSS:3.1/AV:N/AC:H/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 ASE plugin is installed
    Check the WordPress plugins directory (wp-content/plugins) for the 'admin-site-enhancements' folder, or query the wp_options table for 'active_plugins'
    Affected if ASE plugin folder exists in wp-content/plugins or plugin is active in WordPress
  2. Check installed ASE plugin version
    Read the plugin header comment from admin-site-enhancements.php file, or look up the plugin in WordPress Plugins admin page
    Affected if Version number is present and less than 8.8.4 (e.g., 8.8.3, 8.8.2, etc.)
  3. Identify if role demotion/restoration features exist
    Examine the ASE plugin files for role-related handlers, specifically files containing 'role' and 'restore' or 'demotion' functionality in the plugin directory
    Affected if Plugin contains role manipulation code paths that handle administrator account demotion and restoration
  4. Detect presence of demoted administrator accounts
    Query the wp_usermeta table for users with wp_capabilities meta_value containing 'editor' or subscriber' while their user_level is 0, or check for users who previously held administrator roles
    Affected if Any WordPress user account shows a current role lower than a previously assigned administrator role, indicating a demoted admin exists as a potential restoration target

Your environment is affected if the ASE plugin version is below 8.8.4 AND the plugin includes role manipulation features AND demoted administrator accounts exist in the WordPress user database.

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 Admin and Site Enhancements (ASE) plugin to version 8.8.4 or later to include the complete fix for all WordPress role API demotion paths.

Recommended fix High confidence

Admin and Site Enhancements (ASE) and admin-site-enhancements-pro version 8.8.4

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Admin and Site Enhancements (ASE)' or 'admin-site-enhancements-pro'
  4. Check the current version installed
  5. If version is lower than 8.8.4, click 'Update Now' to upgrade to version 8.8.4
  6. Alternatively, download version 8.8.4 from WordPress.org or the vendor and upload/install manually
  7. Verify the update was successful by confirming the new version number

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
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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