# CVE-2026-15909: RafyMrX TOKO-ONLINE-ROTI add.php authorization

> Remote attackers can bypass authorization in the add.php file of the TOKO-ONLINE-ROTI web application by manipulating the kd_cs argument.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **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:** 16 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-f4xv-85hg-mw5r

## What is CVE-2026-15909?

CVE-2026-15909 is a medium-severity authentication bypass vulnerability in RafyMrX TOKO-ONLINE-ROTI, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in RafyMrX TOKO-ONLINE-ROTI up to ddfe1cd587be0a0b5135d8b6e85cce2ec3aece99. Affected is an unknown function of the file proses/add.php. The manipulation of the argument kd_cs leads to authorization bypass. The attack is possible to be carried out remotely. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-15909 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15909 is a medium-severity authentication bypass vulnerability in RafyMrX TOKO-ONLINE-ROTI, published on 16 Jul 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-15909 in the wild and no public exploit code.

Affected product: RafyMrX TOKO-ONLINE-ROTI. 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-15909/ (Markdown: https://insights.sbomify.com/CVE-2026-15909/index.md)
```

## Sources

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

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