# CVE-2026-69703: Atlas-Livre Unauthenticated Access via Admin Controllers Missing Exit

> Unauthenticated attackers can bypass session checks in Atlas-Livre admin controllers to execute destructive actions like record deletion.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-vcrm-cmp2-rj83

## What is CVE-2026-69703?

CVE-2026-69703 is a critical missing authorization vulnerability in maximeAmini Atals-Livre, published on 4 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Atlas-Livre contains an improper access control vulnerability in the admin controllers under Espace_admin/controleur/ that allows unauthenticated attackers to bypass session-based authentication guards by sending raw HTTP requests that ignore redirects. Attackers can invoke destructive admin actions such as record deletion by requesting controller endpoints with GET parameters like supp, because the PHP header() redirect is never followed by an exit or die call, allowing all subsequent code including database operations to execute regardless of session state.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-69703 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-69703 is a critical missing authorization vulnerability in maximeAmini Atals-Livre, published on 4 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-69703 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-69703/ (Markdown: https://insights.sbomify.com/CVE-2026-69703/index.md)
```

## Sources

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

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