# CVE-2026-93870: Cotonti through 1.0.0 Cross-Site Request Forgery in the Ratings Plugin AJAX Handler

> Attackers can forge ratings on behalf of authenticated users in Cotonti CMS by exploiting missing CSRF validation in the ratings plugin.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/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:** 18 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-7h6q-853g-5r6c

## What is CVE-2026-93870?

CVE-2026-93870 is a medium-severity vulnerability in Cotonti, published on 18 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 fails to validate anti-CSRF tokens in the ratings plugin AJAX handler, allowing attackers to forge ratings on behalf of authenticated users. Attackers can craft malicious pages that auto-submit POST requests to modify stored rating data when visited by logged-in users.

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

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


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

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

## Is CVE-2026-93870 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93870 is a medium-severity vulnerability in Cotonti, published on 18 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93870 exists.

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

## Sources

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

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