dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-66428

HIGH · 8.8 CVSS v3.1 Published 2026-01-22
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
An issue with WordPress directory names in WebPros WordPress Toolkit before 6.9.1 allows privilege escalation.

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

WebPros WordPress Toolkit before version 6.9.1 contains a vulnerability related to improper handling of WordPress directory names that enables an authenticated attacker to escalate privileges, likely through path traversal or improper validation of directory paths used by the WordPress management features.

MitigationUpgrade WebPros WordPress Toolkit to version 6.9.1 or later to patch the privilege escalation vulnerability. Review user access controls and audit existing WordPress installations for signs of exploitation.

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 WebPros WordPress Toolkit is installed
    Check for the presence of WebPros WordPress Toolkit on the system. This is commonly bundled with Plesk hosting control panel. Look for the toolkit components in /usr/local/psa or similar control panel directories, or check the control panel interface for WordPress Toolkit features.
    Affected if The product is installed and the version is below 6.9.1
  2. Determine installed version of WordPress Toolkit
    Access the hosting control panel (such as Plesk) and navigate to WordPress Toolkit, or use command-line tools if available: plesk bin wordpress -v or check /usr/local/psa/admin/plib/modules/wordpress/version for version file. Alternatively, check the control panel's modules/plugins listing for the WordPress Toolkit version.
    Affected if The installed version is any version before 6.9.1 (e.g., 6.9.0, 6.8.x, earlier versions)
  3. Confirm WordPress management features are in use
    Check if any WordPress instances are managed by the toolkit. In Plesk, go to WordPress Toolkit and list all managed WordPress installations. The vulnerability affects directory handling in these management features.
    Affected if WordPress installations are being managed and the toolkit version is vulnerable
  4. Inspect WordPress user accounts for privilege escalation signs
    For each WordPress site managed by the toolkit, review the wp_users and wp_usermeta tables in the database. Look for unexpected administrator accounts, changes to user_roles, or modifications to user_capabilities that could indicate privilege escalation has occurred.
    Affected if Unexpected administrator accounts exist or user capabilities have been modified without authorization

The environment is affected if WebPros WordPress Toolkit is installed with a version earlier than 6.9.1 and WordPress installations are managed by the toolkit.

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

Upgrade WebPros WordPress Toolkit to version 6.9.1 or later to patch the privilege escalation vulnerability. Review user access controls and audit existing WordPress installations for signs of exploitation.

Recommended fix Moderate confidence

WebPros WordPress Toolkit 6.9.1 or later

  1. Access the Plesk admin panel or use the Plesk update mechanism
  2. Locate WordPress Toolkit in the Plesk extensions or tools section
  3. Check the current version of WebPros WordPress Toolkit
  4. If the version is earlier than 6.9.1, initiate an upgrade to the latest available version
  5. Verify the upgrade completed successfully and the new version is 6.9.1 or later
  6. Test that WordPress installations can be managed properly after the upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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