# CVE-2025-6461: Information disclosure in CubeWP Framework

> Unauthenticated attackers can extract data from password protected, private, or draft posts via the search feature in the CubeWP WordPress plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jan 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-g9j4-wcw8-q372

## What is CVE-2025-6461?

CVE-2025-6461 is a medium-severity vulnerability in cubewp1211 CubeWP Framework, published on 25 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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 search feature in class-cubewp-search-ajax-hooks.php 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-6461?


## How do I fix CVE-2025-6461?

No fix has been published for CVE-2025-6461 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-6461 being exploited?

There is no known exploitation of CVE-2025-6461 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6461 and fix it if it is affected.

What it is: CVE-2025-6461 is a medium-severity vulnerability in cubewp1211 CubeWP Framework, published on 25 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-6461 in the wild and no public exploit code.

Affected product: cubewp1211 CubeWP Framework. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-6461/ (Markdown: https://insights.sbomify.com/CVE-2025-6461/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-6461
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-6461
- OSV: https://osv.dev/vulnerability/CVE-2025-6461

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-6461/
Summaries are generated and may contain mistakes; the official description above is the record.