# CVE-2026-69091: Admidio before 5.0.11 Authentication Bypass via forum.php

> Unauthenticated attackers can read forum topics and posts in Admidio when login-only mode is enabled due to missing access control validation.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/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:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-cf48-6jrq-gjcm, GHSA-qjhq-374q-29q9

## What is CVE-2026-69091?

CVE-2026-69091 is a high-severity authentication bypass vulnerability in admidio, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Admidio before 5.0.11 contains an authentication bypass vulnerability in the forum module when configured in login-only mode. The access control logic in modules/forum.php fails to validate the login-only configuration state, allowing unauthenticated attackers to read forum topics and posts by directly accessing the module with read-only parameters.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-69091 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-69091 is a high-severity authentication bypass vulnerability in admidio, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-69091 in the wild and no public exploit code.

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

## Sources

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

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