dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-57625

CRITICAL · 9.6 CVSS v3.1 Published 2026-07-02
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 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
Unauthenticated Cross Site Scripting (XSS) in Admin and Site Enhancements (ASE) Pro <= 8.8.5 versions.

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

An unauthenticated Cross Site Scripting (XSS) vulnerability exists in the Admin and Site Enhancements (ASE) Pro WordPress plugin affecting versions 8.8.5 and below. The flaw allows remote attackers to inject malicious scripts into the site without authentication, potentially leading to session hijacking, credential theft, or malware distribution.

MitigationUpdate ASE Pro to a version newer than 8.8.5 once the patch is released. In the interim, consider disabling the plugin or implementing WAF rules to block XSS attack patterns.

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 Pro plugin is installed
    Navigate to WordPress admin > Plugins. Look for 'Admin and Site Enhancements (ASE) Pro' in the installed plugins list.
    Affected if The plugin is not present on the system.
  2. Check installed ASE Pro version
    In WordPress admin > Plugins, locate the ASE Pro plugin and view the version number displayed beneath the plugin name. Alternatively, check the plugin header in /wp-content/plugins/admin-site-enhancements-pro/ folder by opening the main plugin PHP file and looking for 'Version:' in the file header.
    Affected if The installed version is 8.8.5 or any version below 8.8.5.
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify that the ASE Pro plugin has an 'Active' status. The vulnerability requires the plugin to be active to be exploitable.
    Affected if The plugin is installed but currently deactivated - the XSS flaw cannot be triggered while the plugin is inactive.
  4. Check for unauthorized admin accounts
    In WordPress admin > Users, review the list of registered administrators. Look for any unfamiliar or suspicious user accounts that may have been created via the XSS vulnerability.
    Affected if Unexpected admin-level user accounts exist that you did not create.
  5. Review site for injected scripts
    Use browser developer tools or search the WordPress database (wp_posts, wp_options tables) for common XSS payloads like '<script>', 'javascript:', or encoded variations. Also check recent posts and pages for suspicious inline scripts.
    Affected if Malicious script tags or event handlers are found in site content or database entries.

The environment is affected if ASE Pro version 8.8.5 or below is installed and active, exposing the site to unauthenticated XSS attacks.

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 ASE Pro to a version newer than 8.8.5 once the patch is released. In the interim, consider disabling the plugin or implementing WAF rules to block XSS attack patterns.

Recommended fix Moderate confidence

ASE Pro version 8.8.6 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find 'Admin and Site Enhancements (ASE) Pro' in the plugin list
  4. 4. Check if an update is available for the plugin
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. After updating, verify the plugin is running version 8.8.6 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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