# CVE-2026-29206: SQL injection in WP Squared

> Attackers can execute SQL commands as root via the sqloptimizer script if Slow Query logging is enabled, leading to potential privilege escalation.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-7pf6-43fc-mx36

## What is CVE-2026-29206?

CVE-2026-29206 is a high-severity SQL injection vulnerability in WebPros WP Squared, published on 13 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Insufficient sanitization of SQL queries in the `sqloptimizer` utility script allows SQL Injections on behalf of the root user if Slow Query logging is enabled.

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

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


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

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

## Is CVE-2026-29206 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-29206 is a high-severity SQL injection vulnerability in WebPros WP Squared, published on 13 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-29206 in the wild and no public exploit code.

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

## Sources

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

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