CVE-2025-8900

Doccure Core < 1.5.4 - Unauthenticated Privilege Escalation

2025-10-31 18:22
Alyudin Nafiie

Strategic Overview

Status
Patched in 1.5.4
Affected Plugin
Doccure Core
Affected Version
< 1.5.4
CVSS
9.8Critical
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2025-8900
View all Doccure Core vulnerabilities

At a glance

CVE-2025-8900 is a critical-severity Improper Privilege Management vulnerability in the Doccure Core WordPress plugin, affecting versions < 1.5.4. 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.5.4; sites on affected versions should update now. Disclosed October 2025, reported by Alyudin Nafiie.

Vulnerability Overview

The Doccure Core plugin for WordPress is vulnerable to privilege escalation in versions up to, and excluding, 1.5.4. This is due to the plugin allowing users who are registering new accounts to set their own role or by supplying 'user_type' field. This makes it possible for unauthenticated attackers to gain elevated privileges by creating an account with the administrator role.

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

Doccure Core < 1.5.4 carries this weakness at user_type, 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 Doccure Core the fix is 1.5.4: builds < 1.5.4 are affected, anything from 1.5.4 onward is not.

Remediation

Update to version 1.5.4, 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: Doccure Core 1.5.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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