CVE-2025-6254: Critical Privilege Escalation in Doctreat Core WordPress Plugin
The Doctreat Core WordPress plugin contains a critical flaw in its user registration function that fails to validate the role assigned to new users. An attacker can register a new account and assign themselves administrator privileges without needing to authenticate first. This bypasses all normal access controls and gives an attacker complete control over the WordPress site immediately upon registration.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 9.8 CRITICAL · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weaknesses (CWE)
- CWE-269
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-10 / 2026-06-17
NVD description (verbatim)
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.
2 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2025-6254 is a privilege escalation vulnerability in the Doctreat Core plugin affecting versions 1.6.8 and earlier. The vulnerability exists in the doctreat_process_registration() function, which processes user registration requests but does not properly restrict or validate the user role parameter. An unauthenticated attacker can craft a registration request specifying the 'administrator' role, and the function will create the account with those privileges. The vulnerability maps to CWE-269 (Improper Access Control), allowing direct assumption of administrative capabilities without prior authentication or authorization checks.
Business impact
This vulnerability poses an immediate and severe threat to any WordPress site running the affected Doctreat Core plugin. An attacker can register as an administrator within minutes of discovering a vulnerable installation, then modify site content, install malicious plugins, access sensitive data, create persistent backdoors, or completely deface the site. Organizations relying on this plugin for user management face potential data breaches, regulatory compliance violations, and operational disruption. The ease of exploitation and lack of authentication requirements mean that automated scanning and mass exploitation are likely.
Affected systems
Doctreat Core plugin for WordPress, all versions up to and including 1.6.8. The vulnerability affects any WordPress installation with this plugin active, regardless of site size, hosting provider, or configuration. No specific WordPress core version requirements have been identified that would limit exposure.
Exploitability
This vulnerability is trivial to exploit. An attacker requires no prior access, no credentials, and no user interaction from victims. The attack is entirely network-based with no complexity. An attacker can perform the privilege escalation in a single HTTP request to the plugin's registration endpoint, specifying administrator role parameters. The lack of CAPTCHA, rate limiting, or role validation in the vulnerable function means automated exploitation at scale is feasible. Given the CVSS 3.1 vector of AV:N/AC:L/PR:N/UI:N, this represents a weaponizable flaw.
Remediation
Immediately update the Doctreat Core plugin to a version after 1.6.8. Verify against the vendor's official advisory for the patched version number. If an immediate patch is unavailable, consider disabling the plugin entirely until a fixed version is released. For sites that cannot update immediately, restrict access to the plugin's registration endpoint using Web Application Firewall (WAF) rules or server-level authentication. Review user accounts created during the potential exposure window for unauthorized administrator accounts and audit their activity logs.
Patch guidance
Check the Doctreat Core plugin repository or vendor advisory for the first available version after 1.6.8 that addresses this issue. Apply the patch through the WordPress admin dashboard (Plugins > Installed Plugins > Update) or manually via SFTP/file manager. Test the update in a staging environment first to ensure compatibility with other plugins and custom themes. After patching, audit the wp_users table for unexpected administrator accounts created during the vulnerability window, and review administrator access logs for suspicious activity.
Detection guidance
Monitor WordPress user registration logs and wp_users table additions for new administrator accounts created without corresponding administrative action in audit logs. In WAF or server logs, look for POST requests to registration endpoints specifying administrator role parameters. Check for rapid account creation patterns suggesting automated exploitation attempts. Review the access logs for the plugin's registration functions (typically /wp-admin/admin-ajax.php with doctreat_process_registration action) for unusual traffic spikes or geographically anomalous sources. Ensure WordPress user creation audit logging is enabled and monitored continuously.
Why prioritize this
This vulnerability merits immediate attention due to its CRITICAL severity (CVSS 9.8), complete lack of authentication requirements (PR:N), and direct path to full site compromise. Unlike vulnerabilities requiring user interaction or special access, this flaw allows complete administrative takeover in seconds. Organizations running Doctreat Core should treat this as an emergency requiring immediate patching or plugin disabling. The ease of exploitation means that delayed response significantly increases the likelihood of active compromise.
Risk score, explained
The CVSS 3.1 score of 9.8 reflects the confluence of maximum exploitability factors: network-accessible endpoint (AV:N), no authentication required (PR:N), no user interaction needed (UI:N), and unrestricted scope (S:U). The impact is total across all three security properties—an attacker gains full confidentiality, integrity, and availability compromise (C:H/I:H/A:H). The only factor preventing a perfect 10.0 score is the requirement for the plugin to be actively installed, which is a deployment factor rather than a flaw in the vulnerability itself.
Frequently asked questions
Can this vulnerability be exploited if the Doctreat Core plugin is installed but not activated?
No. The plugin must be activated for the vulnerable registration function to be callable. However, it is a best practice to remove unused plugins entirely rather than simply deactivating them.
Does updating WordPress core or other plugins fix this vulnerability?
No. This is a flaw within the Doctreat Core plugin itself. Only updating or removing the Doctreat Core plugin will resolve the issue. WordPress core updates and other plugin updates do not address this specific vulnerability.
If an attacker created an administrator account on our site, can we detect and remove the malicious account?
Yes, but verification requires care. Review the wp_users table and wp_usermeta table for administrator accounts created during the exposure window. Check user creation timestamps against your WordPress activity logs and backup records to identify suspicious accounts. Remove only confirmed unauthorized accounts and immediately reset passwords for all legitimate administrators. Conduct a full site audit for backdoors, malicious plugins, and unauthorized configuration changes that the attacker may have installed.
Is there a workaround if we cannot update immediately?
Disable the Doctreat Core plugin immediately if a patch is not yet available. If disabling is not an option, use a WAF rule to block requests to the vulnerable registration endpoint, or use server-level authentication to restrict access to wp-admin/admin-ajax.php. However, these are temporary measures only—apply the official patch as soon as it becomes available.
This analysis is based on the CVE record published on 2026-06-10 and modified 2026-06-17. Verify all patch version numbers against the official vendor advisory before applying updates. This vulnerability assessment does not constitute a comprehensive security audit. Organizations should conduct their own vulnerability scanning, testing, and risk analysis tailored to their specific environment. SEC.co makes no warranty regarding the completeness or accuracy of remediation steps and recommends consultation with security professionals for complex environments. The information herein is for educational and defensive purposes only. Source: NVD (public-domain), retrieved 2026-07-19. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2024-38487HIGHapi-gateway Container Escape via Root Privilege Mismanagement
- CVE-2025-31272HIGHmacOS Launch Constraint Bypass and Local Privilege Escalation
- CVE-2025-5088HIGHCVX Redis Privilege Escalation to Root Access
- CVE-2025-9912MEDIUMNokia SR Linux Local Privilege Escalation
- CVE-2026-0009HIGHAndroid Tapjacking Local Privilege Escalation Vulnerability
- CVE-2026-0016LOWAndroid Credential Manager Permission Bypass & Cross-User Data Disclosure
- CVE-2026-0046MEDIUMAndroid Tapjacking Permission Escalation Vulnerability
- CVE-2026-0048MEDIUMAndroid Tapjacking Vulnerability – Privilege Escalation via WindowState
Preview — this page is review (quality 0.935). high-value: hold for review.