CVE-2025-6254

Doctreat Core <= 1.6.8 - Unauthenticated Privilege Escalation

2026-06-09 20:15
Foxyyy

Strategic Overview

Status
Patched in 1.7.0
Affected Plugin
Doctreat Core
Affected Version
<= 1.6.8
CVSS
9.8Critical
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2025-6254
View all Doctreat Core vulnerabilities

At a glance

CVE-2025-6254 is a critical-severity Improper Privilege Management vulnerability in the Doctreat Core WordPress plugin, affecting versions <= 1.6.8. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.7.0; sites on affected versions should update now. Disclosed June 2026, reported by Foxyyy.

Vulnerability Overview

The Doctreat Core plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.6.8. This is due to the doctreat_process_registration() function not properly restricting the roles that a user can register with. This makes it possible for unauthenticated attackers to register as an administrator user.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-269: Improper Privilege Management

Doctreat Core <= 1.6.8 carries this weakness at doctreat_process_registration(), and reaching it takes no account at all. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For Doctreat Core the fix is 1.7.0: builds <= 1.6.8 are affected, anything from 1.7.0 onward is not.

Remediation

Update to version 1.7.0, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Doctreat Core 1.7.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C