# CVE-2026-69704: Atals-Livre SQL Injection via Unsanitized GET Parameter in supp()

> Attackers can inject SQL via GET parameters to delete or extract database data in Atals-Livre applications.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-w8hf-r35f-2h3j

## What is CVE-2026-69704?

CVE-2026-69704 is a high-severity SQL injection vulnerability in maximeAmini Atals-Livre, published on 4 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Atals-Livre contains a SQL injection vulnerability that allows attackers to manipulate database queries by passing unsanitized input through a GET parameter to the supp() deletion helper function. Attackers can inject malicious SQL syntax via the vulnerable GET parameter to perform unauthorized database operations including data deletion and extraction.

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

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


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

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

## Is CVE-2026-69704 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-69704 is a high-severity SQL injection vulnerability in maximeAmini Atals-Livre, published on 4 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-69704 exists.

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

## Sources

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

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