CVE-2026-57692

Private Content <= 9.9.2 - Unauthenticated Privilege Escalation

2026-07-01 00:00
0xd4rk5id3

Strategic Overview

Status
Unpatched
Affected Plugin
Private Content
Affected Version
<= 9.9.2
CVSS
9.8Critical
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2026-57692
View all Private Content vulnerabilities

At a glance

CVE-2026-57692 is a critical-severity Improper Privilege Management vulnerability in the Private Content WordPress plugin, affecting versions <= 9.9.2. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed July 2026, reported by 0xd4rk5id3.

Vulnerability Overview

The Private Content plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 9.9.2. This makes it possible for unauthenticated attackers to elevate their privileges to that of an administrator.

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

Reaching this weakness in Private Content <= 9.9.2 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. No fixed build of this plugin is recorded for Private Content yet, so installs running <= 9.9.2 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-57692https://www.wordfence.com/threat-intel/vulnerabilities/id/50bdca4a-23c0-46aa-8c08-5987a2e28604https://nvd.nist.gov/vuln/detail/CVE-2026-57692

Related records

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