# CVE-2026-73331: CamaleonCMS 2.9.1 Authenticated SQL Injection via Post Slug Field

> Authenticated attackers with post editing privileges can exploit SQL injection in the slug field to extract sensitive data from the database.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA: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:** 12 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-rvgr-q8fx-r93h

## What is CVE-2026-73331?

CVE-2026-73331 is a high-severity SQL injection vulnerability in owen2345 CamaleonCMS, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CamaleonCMS 2.9.1 contains an authenticated SQL injection vulnerability that allows authenticated attackers with post creation or editing privileges to submit a crafted slug value containing SQL syntax that the database backend evaluates as part of an inadequately parameterized query. Attackers can supply malicious slug payloads using boolean- or union-style blind SQL injection techniques to extract sensitive data from the underlying SQLite database, including administrative credentials and configuration values stored in application tables.

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

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


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

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

## Is CVE-2026-73331 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73331 is a high-severity SQL injection vulnerability in owen2345 CamaleonCMS, published on 12 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-73331 in the wild and no public exploit code.

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

## Sources

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

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