CVE-2025-12129
BaseFortify
Publication date: 2026-01-17
Last updated on: 2026-01-17
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| cubewp | cubewp_all-in-one_dynamic_content_framework | to 1.1.27 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-200 | The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in the CubeWP WordPress plugin affects its REST API endpoints (/cubewp-posts/v1/query-new and /cubewp-posts/v1/query). Due to insufficient permission checks, unauthenticated attackers could access data from password protected, private, or draft posts that should not be publicly accessible. The plugin originally allowed unrestricted public access to these endpoints, exposing sensitive post content and metadata. The issue arises because the API did not properly enforce WordPress post visibility and user capability rules, leading to unauthorized information exposure. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the CubeWP plugin to version 1.1.28 or later, which includes security fixes that enforce proper permission checks on the REST API endpoints and prevent unauthorized access to protected post data. [1]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized disclosure of sensitive information stored in WordPress posts, including password protected, private, or draft content. Attackers without authentication can extract this data via the REST API, potentially exposing confidential or unpublished information. This could result in privacy breaches, loss of intellectual property, or reputational damage if sensitive content is leaked. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by attempting to access the REST API endpoints /cubewp-posts/v1/query-new and /cubewp-posts/v1/query on your WordPress site without authentication and checking if data from password protected, private, or draft posts is exposed. For example, you can use curl commands like: curl -X GET https://yourwordpresssite.com/wp-json/cubewp-posts/v1/query and curl -X GET https://yourwordpresssite.com/wp-json/cubewp-posts/v1/query-new and inspect the response for unauthorized post data exposure. [1]