# CVE-2026-82658: Admidio before 5.0.12 Broken Access Control via profile_function.php

> Authenticated low-privilege users can bypass authorization to read other users' future role memberships in Admidio.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 30 Aug 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-4p3x-3rxj-v7c4, GHSA-7mr9-2w6x-hw8r

## What is CVE-2026-82658?

CVE-2026-82658 is a medium-severity missing authorization vulnerability in admidio, published on 30 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Admidio versions before 5.0.12 contain a broken access control vulnerability in profile_function.php that allows authenticated low-privilege users to read another user's future role memberships. Attackers can bypass profile-level authorization by directly calling the reload_future_memberships endpoint with a victim's user UUID to disclose sensitive membership information.

Weakness: CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-82658 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82658 is a medium-severity missing authorization vulnerability in admidio, published on 30 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82658 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-82658/ (Markdown: https://insights.sbomify.com/CVE-2026-82658/index.md)
```

## Sources

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

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