# CVE-2026-69090: Admidio before 5.0.11 Cross-Organization Role Modification

> Authenticated role administrators can modify roles in other organizations by supplying external UUIDs, bypassing organizational boundaries.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-fcq9-w4hp-xchg, GHSA-jq7q-39fg-c24g

## What is CVE-2026-69090?

CVE-2026-69090 is a medium-severity missing authorization vulnerability in admidio, published on 3 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Admidio before 5.0.11 fails to validate target organization membership in role handlers, allowing authenticated role administrators to delete, activate, deactivate, or edit roles belonging to other organizations. Attackers can supply a role UUID from another organization to groups_roles.php handlers to modify that organization's roles without authorization.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-69090 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-69090 is a medium-severity missing authorization vulnerability in admidio, published on 3 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-69090 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-2026-69090/ (Markdown: https://insights.sbomify.com/CVE-2026-69090/index.md)
```

## Sources

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

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