# CVE-2018-25370: Admidio 3.3.5 Cross-Site Request Forgery via roles_function.php

> Attackers can exploit CSRF in Admidio to escalate privileges by tricking users into submitting malicious forms.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 May 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-76g9-r7wc-v9q8

## What is CVE-2018-25370?

CVE-2018-25370 is a medium-severity vulnerability in Admidio, published on 25 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Admidio 3.3.5 contains a cross-site request forgery vulnerability that allows low-privilege users to increase their permissions by exploiting improper origin checking. Attackers can craft malicious HTML forms targeting roles_function.php with parameters like rol_assign_roles, rol_approve_users, and rol_edit_user set to 1 to escalate privileges without authentication.

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

## Which versions are affected by CVE-2018-25370?


## How do I fix CVE-2018-25370?

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

## Is CVE-2018-25370 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25370 and fix it if it is affected.

What it is: CVE-2018-25370 is a medium-severity vulnerability in Admidio, published on 25 May 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-2018-25370 exists.

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

## Sources

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

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