# CVE-2026-17017: CubeWP Framework < 1.1.31 - Subscriber+ SQL Injection via cubewp_remove_relation

> Subscribers can perform SQL injection via an unsanitized AJAX parameter in the CubeWP Framework plugin, allowing unauthorized database access.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 9 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-6hh8-5xhj-2p65

## What is CVE-2026-17017?

CVE-2026-17017 is a high-severity SQL injection vulnerability in Unknown CubeWP Framework, published on 9 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The CubeWP Framework WordPress plugin before 1.1.31 does not properly sanitize and escape a parameter before using it in a SQL statement through an AJAX action, and does not include a capability check on that action, allowing users with Subscriber-level access and above to perform SQL injection attacks.

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

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


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

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

## Is CVE-2026-17017 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-17017 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17017 is a high-severity SQL injection vulnerability in Unknown CubeWP Framework, published on 9 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-17017 exists.

Affected product: Unknown 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-17017/ (Markdown: https://insights.sbomify.com/CVE-2026-17017/index.md)
```

## Sources

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

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