admidio/admidio path traversal in file rename lets attackers write files
Only affects Admidio 5.0.0 through 5.0.17 for users with folder upload permission on a documents folder. Fixed in 5.0.18.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.0.18
- Who is exposed
- Specific setups only
Summary
Admidio contains a path traversal flaw in its file rename function that lets a logged-in user with folder upload permission write files and create directories in arbitrary writable locations, including the web root. An attacker can reach it remotely over the network with low-privilege login and no user interaction.
Written by a model
Original description
Admidio from 5.0.0 before 5.0.18 contains a path traversal vulnerability in DocumentsService::renameFile() that allows authenticated users to move files outside adm_my_files by supplying an unvalidated adm_new_name value. Attackers with folder upload permission can submit ../ sequences to file_rename_save to write files and create directories in arbitrary writable locations, including the web root.
Who should check
Teams running Admidio 5.0.0 through 5.0.17 that use the Documents & Files module with folder upload permission.
“Admidio from 5.0.0 before 5.0.18 contains a path traversal vulnerability”
What to do
Check whether your setup matches what the bug needs.
Admidio versions 5.0.0 through 5.0.17 (fixed in 5.0.18). The attacker needs folder upload permission on a documents folder.Upgrade to a fixed version: 5.0.18.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134254 (Admidio 5.0.0 before 5.0.18 Path Traversal via Documents & Files Rename), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134254 (entry last updated 2026-11-21):
Affected:
- Packagist package admidio/admidio: from 5.0.0, fixed in 5.0.18
Fixed versions: 5.0.18.
Conditions (all must be true for the bug to be hit):
- Admidio versions 5.0.0 through 5.0.17 (fixed in 5.0.18). (source: https://www.vulncheck.com/advisories/admidio-5.0.0-before-5.0.18-path-traversal-via-documents-files-rename)
- The attacker needs folder upload permission on a documents folder. (source: https://www.vulncheck.com/advisories/admidio-5.0.0-before-5.0.18-path-traversal-via-documents-files-rename)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134254 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134254 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Packagist): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Admidio/admidio/security/advisories/GHSA-4fqv-v627-2ggm
- https://www.vulncheck.com/advisories/admidio-5.0.0-before-5.0.18-path-traversal-via-documents-files-rename
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134254
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134254"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Packagist packages
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 32 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · Admidio/admidio · Advisory GHSA-4fqv-v627-2ggm |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134254 |
| Record | NVD · CVE-2026-134254 |
| Other links 1 | |
| Link | vulncheck.com · advisories/admidio-5.0.0-before-5.0.18-path-traversal-via-documents-files-rename |
Questions about CVE-2026-134254
Is CVE-2026-134254 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A flaw in the Documents & Files rename function lets an authenticated user submit ../ sequences that escape the intended folder. This can move or create files at arbitrary writable paths on the server, including the web root, and create arbitrary directories.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134254?
admidio/admidio (Packagist): from 5.0.0 before 5.0.18.
Source: cve.now feed data
Am I affected, and how do I check?
Admidio versions 5.0.0 through 5.0.17 are affected, provided the user has folder upload permission on a documents folder. To check, look at the installed Admidio version in the administration area and compare it with 5.0.18.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134254?
Upgrade Admidio to version 5.0.18, which is the fixed version listed for this vulnerability.
Source: vulncheck.com, github.com
Related
- CVE-2026-41670Admidio: SAML Response Sent to Unvalidated Assertion Consumer Service URL from AuthnRequest
- CVE-2026-41669Admidio: SAML Signature Validation Result Ignored — Forged AuthnRequests and LogoutRequests Processed
- CVE-2026-47231Admidio has IDOR in `documents-files.php` `mode=move_save` that lets any folder-uploader exfiltrate files from private folders
- CVE-2026-41660Admidio: Inverted 2FA Reset Authorization Check Lets Group Leaders Strip Admin TOTP
- CVE-2026-42194Incomplete fix for CVE-2026-32812: SSRF in admidio
- CVE-2026-41671Admidio: OIDC Token Introspection Endpoint Returns Active for All Tokens Without Validation
No corrections so far. Something wrong on this page? Report an error.