# CVE-2026-101093: Cotonti through 1.0.0 Cross-Site Request Forgery via User Group Deletion

> Attackers can trick administrators into deleting user groups via CSRF, compromising permission structures in Cotonti CMS.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-mqh8-c67q-h37j

## What is CVE-2026-101093?

CVE-2026-101093 is a medium-severity vulnerability in Cotonti, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cotonti through 1.0.0 contains a cross-site request forgery vulnerability in admin.users.php that allows attackers to delete user groups without token verification. Attackers can craft malicious links or pages that trick authenticated administrators into deleting custom groups and their associated permissions by riding the administrator's session.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-101093 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101093 is a medium-severity vulnerability in Cotonti, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-101093 in the wild and no public exploit code.

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

## Sources

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

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