# CVE-2026-71252: toner-management - Unauthenticated State-Changing Admin Actions

> Unauthenticated attackers can perform administrative database modifications by accessing unprotected state-changing endpoints in the toner-management web application.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-c6wq-2527-5fpx

## What is CVE-2026-71252?

CVE-2026-71252 is a high-severity missing authorization vulnerability in raghav993 toner-management, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

toner-management's admin state-changing handlers (add.php, edit.php, delete.php under admin/toners, admin/toner-brands, admin/printers, and related admin subdirectories) executed INSERT/UPDATE/DELETE database operations with no authentication or authorization check, while access control was enforced only in listing views.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-71252 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71252 is a high-severity missing authorization vulnerability in raghav993 toner-management, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71252 in the wild and no public exploit code.

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

## Sources

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

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