Admidio has Path Traversal in ECard Preview that Allows Reading Arbitrary Server Files Including Database Credentials

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-41655: 0.31% estimated exploitation activity in the next 30 days; percentile 23.57 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The ecardpreview.php endpoint does not validate that the ecardtemplate POST parameter is a safe filename before passing it to ECard::getEcardTemplate(). An authenticated user can supply a path traversal payload (e.g., ../config.php) to read arbitrary files accessible to the web server process, including admmyfiles/config.php which contains database credentials. Details Root Cause: The ecardtemplate parameter is a select box whose value is only sanitized via strStripTags() during form validation, which does not restrict path traversal characters. Unlike ecardsend.php which explicitly validates the template name as a safe filename, ecardpreview.php omits this check entirely. Code Path: 1. modules/photos/ecards.php:143-152 — The form creates a select box with template filenames from admmyfiles/ecardtemplates/. The form object is stored in the session. 2. modules/photos/ecardpreview.php:33-34 — The POST request is validated against the stored form object: 3.…

Published by the source

29 Apr 2026, 21:37 UTC

Last modified by the source

8 May 2026, 19:55 UTC

Source last checked

26 Oct 2026, 14:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-m3vp-3jjm-gpmx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41655

Advisory: Admidio has Path Traversal in ECard Preview that Allows Reading Arbitrary Server Files Including Database Credentials
IDs: CVE-2026-41655, GHSA-m3vp-3jjm-gpmx
Record: https://patchnext.com/advisories/cve-2026-41655 (revision 1, source checked 26 Oct 2026, 14:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: admidio/admidio 5.0.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist admidio/admidio: affected <= 5.0.8; fixed in 5.0.9

## Suggested inspection (read-only)
- Packagist admidio/admidio: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on admidio/admidio.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-m3vp-3jjm-gpmx (GitHub-reviewed advisory GHSA-m3vp-3jjm-gpmx lists affected ranges: Packagist admidio/admidio >=0 <=5.0.8)

Commands are suggestions: review each one before running it.