Admidio has an HTMLPurifier Bypass in eCard Message Allows HTML Email Injection

Exploitation

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

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

EPSS

• CVE-2026-32757: 0.23% estimated exploitation activity in the next 30 days; percentile 14.07 (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 eCard send handler in Admidio uses the raw $POST['ecardmessage'] value instead of the HTMLPurifier-sanitized $formValues['ecardmessage'] when constructing the greeting card HTML. This allows an authenticated attacker to inject arbitrary HTML and JavaScript into greeting card emails sent to other members, bypassing the server-side HTMLPurifier sanitization that is properly applied to the ecardmessage field during form validation. Details Root Cause File: D:\bugcrowd\admidio\repo\modules\photos\ecardsend.php At line 38, the raw POST value is captured BEFORE form validation runs: At line 61, the form validation runs and properly sanitizes the message through HTMLPurifier (since ecardmessage is registered as an editor field): The sanitized value is stored in $formValues['ecardmessage'], but this value is never used. Instead, the raw $postMessage is passed to parseEcardTemplate() at lines 159 and 201: Template Injection File:…

Published by the source

16 Mar 2026, 21:18 UTC

Last modified by the source

20 Mar 2026, 21:15 UTC

Source last checked

26 Oct 2026, 14:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4wr4-f2qf-x5wj

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

# Patch Next advisory brief: CVE-2026-32757

Advisory: Admidio has an HTMLPurifier Bypass in eCard Message Allows HTML Email Injection
IDs: CVE-2026-32757, GHSA-4wr4-f2qf-x5wj
Record: https://patchnext.com/advisories/cve-2026-32757 (revision 1, source checked 26 Oct 2026, 14:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
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.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist admidio/admidio: affected <= 5.0.6; fixed in 5.0.7

## 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-4wr4-f2qf-x5wj (GitHub-reviewed advisory GHSA-4wr4-f2qf-x5wj lists affected ranges: Packagist admidio/admidio >=0 <=5.0.6)

Commands are suggestions: review each one before running it.