# CVE-2026-6453: CubeWP Framework <= 1.1.30 - Authenticated (Subscriber+) SQL Injection via 'relation_id' Parameter

> Authenticated attackers with subscriber access can execute arbitrary SQL queries via the relation_id parameter in the CubeWP Framework plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** 1 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-fg67-hgjg-74qh

## What is CVE-2026-6453?

CVE-2026-6453 is a medium-severity SQL injection vulnerability in cubewp1211 CubeWP Framework, published on 1 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The CubeWP Framework plugin for WordPress is vulnerable to SQL Injection in all versions up to and including 1.1.30. This is due to insufficient input sanitization in the cubewp_remove_relation() AJAX function, specifically the use of wp_unslash() on the relation_id parameter before interpolating it directly into a raw SQL query without using $wpdb->prepare(). The wp_unslash() call explicitly removes the backslash escaping that WordPress's wp_magic_quotes() adds to all $_POST data, neutralizing the only layer of SQL injection protection. The sanitize_text_field() function applied afterward offers no SQL protection. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries to the existing query.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-6453?


## How do I fix CVE-2026-6453?

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

## Is CVE-2026-6453 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6453 and fix it if it is affected.

What it is: CVE-2026-6453 is a medium-severity SQL injection vulnerability in cubewp1211 CubeWP Framework, published on 1 Aug 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-2026-6453 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-2026-6453/ (Markdown: https://insights.sbomify.com/CVE-2026-6453/index.md)
```

## Sources

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

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