CVE-2025-11260

WP Headless CMS Framework <= 1.15 - Unauthenticated Protection Mechanism Bypass

2025-10-14 00:00
Jonas Benjamin Friedli

Strategic Overview

Status
Unpatched
Affected Version
<= 1.15
CVSS
5.3Medium
Weakness type
CWE-693 · Protection Mechanism Failure
CVE
CVE-2025-11260
View all WP Headless CMS Framework vulnerabilities

At a glance

CVE-2025-11260 is a medium-severity Protection Mechanism Failure vulnerability in the WP Headless CMS Framework WordPress plugin, affecting versions <= 1.15. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed October 2025, reported by Jonas Benjamin Friedli.

Vulnerability Overview

The WP Headless CMS Framework plugin for WordPress is vulnerable to protection mechanism bypass in all versions up to, and including, 1.15. This is due to the plugin only checking for the existence of the Authorization header in a request when determining if the nonce protection should be bypassed. This makes it possible for unauthenticated attackers to access content they should not have access to.

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.

CWE-693: Protection Mechanism Failure

The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

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

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