CVE-2025-12129

CubeWP – All-in-One Dynamic Content Framework <= 1.1.27 - Unauthenticated Information Exposure

2026-01-16 19:16
Jonas Benjamin Friedli

Strategic Overview

Status
Patched in 1.1.28
Affected Plugin
CubeWP Framework
Affected Version
<= 1.1.27
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2025-12129
View all CubeWP Framework vulnerabilities

At a glance

CVE-2025-12129 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the CubeWP Framework WordPress plugin, affecting versions <= 1.1.27. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.28; sites on affected versions should update now. Disclosed January 2026, reported by Jonas Benjamin Friedli.

Vulnerability Overview

The CubeWP – All-in-One Dynamic Content Framework plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 1.1.27 via the /cubewp-posts/v1/query-new and /cubewp-posts/v1/query REST API endpoints due to insufficient restrictions on which posts can be included. This makes it possible for unauthenticated attackers to extract data from password protected, private, or draft posts that 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-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in CubeWP Framework <= 1.1.27 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For CubeWP Framework the fix is 1.1.28: builds <= 1.1.27 are affected, anything from 1.1.28 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-12129https://www.wordfence.com/threat-intel/vulnerabilities/id/2006dc4c-ec1a-45ab-94a3-1f86d80e70cahttps://nvd.nist.gov/vuln/detail/CVE-2025-12129

Related records

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