# CVE-2026-32812: Admidio Vulnerable to SSRF and Local File Read via Unrestricted URL Fetch in SSO Metadata Endpoint

> An authenticated administrator can exploit an unrestricted URL fetch in the SSO Metadata endpoint to perform Server-Side Request Forgery and read arbitrary local files.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-6j68-gcc3-mq73

## What is CVE-2026-32812?

CVE-2026-32812 is a medium-severity server-side request forgery vulnerability in admidio, published on 20 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Admidio is an open-source user management solution. In versions 5.0.0 through 5.0.6, unrestricted URL fetch in the SSO Metadata API can result in SSRF and local file reads. The SSO Metadata fetch endpoint at modules/sso/fetch_metadata.php accepts an arbitrary URL via $_GET['url'], validates it only with PHP's FILTER_VALIDATE_URL, and passes it directly to file_get_contents(). FILTER_VALIDATE_URL accepts file://, http://, ftp://, data://, and php:// scheme URIs. An authenticated administrator can use this endpoint to read arbitrary local files via the file:// wrapper (Local File Read), reach internal services via http:// (SSRF), or fetch cloud instance metadata. The full response body is returned verbatim to the caller. This issue has been fixed in version 5.0.7.

Weakness: CWE-918 (Server-Side Request Forgery)

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

2 open source packages ship an affected version, including admidio/admidio. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `admidio/admidio` | Packagist | From 5.0.0 | 5.0.7 |
| `admidio/admidio` | Packagist | From 5.0.0 | 5.0.7 |

Products: Admidio Admidio.

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

Upgrade admidio/admidio to 5.0.7 or later.

## Is CVE-2026-32812 being exploited?

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

## Other vulnerabilities in admidio

- [CVE-2024-37906](https://insights.sbomify.com/CVE-2024-37906/): Admidio has Blind SQL Injection in ecard_send.php (critical 10.0)
- [CVE-2021-32630](https://insights.sbomify.com/CVE-2021-32630/): Various (critical 9.6)
- [CVE-2026-32817](https://insights.sbomify.com/CVE-2026-32817/): Admidio is Missing Authorization and CSRF Protection on Document and Folder Deletion (critical 9.1)
- [CVE-2024-38529](https://insights.sbomify.com/CVE-2024-38529/): Admidio Vulnerable to RCE via Arbitrary File Upload in Message Attachment (critical 9.1)
- [CVE-2026-32756](https://insights.sbomify.com/CVE-2026-32756/): Admidio: Unrestricted File Upload via CSRF Token Validation Bypass in Documents & Files Module (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32812 is a medium-severity server-side request forgery vulnerability in admidio, published on 20 Mar 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-32812 exists.

Affected packages and fixed versions:
- admidio/admidio (Packagist): affected from 5.0.0; fixed in 5.0.7
- admidio/admidio (Packagist): affected from 5.0.0; fixed in 5.0.7

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

## Sources

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

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