# CVE-2026-86293: SourceCodester Simple Traffic Offense System Deletion Endpoint delete-user.php missing authentication

> Remote attackers can delete users without authentication by manipulating the ID parameter in the delete-user.php endpoint.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-jvx9-crv4-28cj

## What is CVE-2026-86293?

CVE-2026-86293 is a medium-severity missing authorization vulnerability in SourceCodester Simple Traffic Offense System, published on 7 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw has been found in SourceCodester Simple Traffic Offense System 1.0. Affected by this vulnerability is an unknown functionality of the file delete-user.php of the component Deletion Endpoint. Executing a manipulation of the argument ID can lead to missing authentication. The attack may be launched remotely. The exploit has been published and may be used.

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

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


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

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

## Is CVE-2026-86293 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86293 is a medium-severity missing authorization vulnerability in SourceCodester Simple Traffic Offense System, published on 7 Sep 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-86293 exists.

Affected product: SourceCodester Simple Traffic Offense System. 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-86293/ (Markdown: https://insights.sbomify.com/CVE-2026-86293/index.md)
```

## Sources

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

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