CVE-2025-12129
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe CubeWP WordPress plugin has insufficient authorization controls on its REST API endpoints (/cubewp-posts/v1/query-new and /cubewp-posts/v1/query), allowing unauthenticated attackers to query and retrieve content from password-protected, private, or draft posts that should be restricted.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if CubeWP plugin is installedNavigate to WordPress admin dashboard > Plugins, or inspect the /wp-content/plugins/cubewp-framework/ directory to confirm the plugin is present and activeAffected if CubeWP plugin is not installed or not active - not affected
-
Determine the installed CubeWP versionIn WordPress admin > Plugins > CubeWP Framework, read the version number displayed; alternatively, check the main plugin file header in /wp-content/plugins/cubewp-framework/cubewp.php for the 'Version' tagAffected if Version is unknown or cannot be determined - assume potentially affected
-
Compare version to the fixed releaseCompare your installed version against 1.1.28: versions below 1.1.28 are vulnerable; versions 1.1.28 and above include the fixAffected if Installed version is lower than 1.1.28 - vulnerable and affected
-
Verify REST API endpoint accessibilitySend a GET request to /wp-json/cubewp-posts/v1/query or /wp-json/cubewp-posts/v1/query-new without authentication cookies or auth tokens, using curl or browser dev toolsAffected if Endpoint returns valid JSON response to unauthenticated request - vulnerability is exploitable in your environment
You are affected if CubeWP version is below 1.1.28 and the plugin REST API endpoints respond to unauthenticated requests, allowing access to restricted post content.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to version 1.1.28 or later which contains proper authorization checks, or implement endpoint-level capability checks to verify user permissions before returning post data.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12129 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-12129 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data