# CVE-2026-47232: Admidio PKCS#12 private key export action lacks CSRF protection

> Attackers can force administrators to export sensitive private keys via forged requests due to missing CSRF protection in Admidio.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-4rgq-38mh-9xqg

## What is CVE-2026-47232?

CVE-2026-47232 is a medium-severity vulnerability in admidio, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Admidio is an open-source user management solution. Prior to version 5.0.10, the sensitive `mode=export` action in `modules/sso/keys.php` exports a PKCS#12 bundle containing the configured private key and certificate, but the CSRF validation line is commented out. A forged cross-site POST from an administrator session can therefore trigger private key export without a valid form token. Version 5.0.10 contains a fix.

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

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

2 open source packages ship an affected version, including admidio/admidio.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `admidio/admidio` | Packagist | All versions | 5.0.10 |
| `admidio/admidio` | Packagist | All versions | 5.0.10 |

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

Upgrade admidio/admidio to 5.0.10 or later.

## Is CVE-2026-47232 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47232 is a medium-severity vulnerability in admidio, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47232 exists.

Affected packages and fixed versions:
- admidio/admidio (Packagist): affected all versions; fixed in 5.0.10
- admidio/admidio (Packagist): affected all versions; fixed in 5.0.10

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

## Sources

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

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