ghsa-x82r-6j37-vrgg
Vulnerability from github
Summary
An HTML injection issue allows users with access to the email sending functionality to inject arbitrary HTML code into emails sent via the admin interface, potentially leading to session cookie theft and the alteration of page content.
Details
The vulnerability was discovered in the /admin/email/send-test-email
endpoint using the POST
method. The vulnerable parameter is content
, which permits the injection of arbitrary HTML code during the email sending process. While JavaScript code injection is blocked through filtering, HTML code injection remains possible.
PoC
To reproduce the vulnerability, a user must fill out the email's content form with the desired HTML payload.
Impact
This HTML injection vulnerability can potentially enable phishing attacks by allowing the insertion of any html like fake login forms, etc.
All functionalities that process user input should be carefully reviewed to ensure that data is appropriately encoded as HTML entities in server responses. For instance, a reflected input paramete like <h1> just a test </h1> <p> <img>
should be displayed in the HTML response as <h1> just a test </h1> <p> <img>
.
{ "affected": [ { "package": { "ecosystem": "Packagist", "name": "pimcore/admin-ui-classic-bundle" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "1.7.6" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2025-30166" ], "database_specific": { "cwe_ids": [ "CWE-79" ], "github_reviewed": true, "github_reviewed_at": "2025-04-08T14:51:41Z", "nvd_published_at": "2025-04-08T11:15:44Z", "severity": "LOW" }, "details": "### Summary\nAn HTML injection issue allows users with access to the email sending functionality to inject arbitrary HTML code into emails sent via the admin interface, potentially leading to session cookie theft and the alteration of page content.\n\n### Details\nThe vulnerability was discovered in the `/admin/email/send-test-email` endpoint using the `POST` method. The vulnerable parameter is `content`, which permits the injection of arbitrary HTML code during the email sending process. While JavaScript code injection is blocked through filtering, HTML code injection remains possible.\n\n### PoC\nTo reproduce the vulnerability, a user must fill out the email\u0027s content form with the desired HTML payload.\n\n\n### Impact\n\n\nThis HTML injection vulnerability can potentially enable phishing attacks by allowing the insertion of any html like fake login forms, etc.\nAll functionalities that process user input should be carefully reviewed to ensure that data is appropriately encoded as HTML entities in server responses. For instance, a reflected input paramete like `\u003ch1\u003e just a test \u003c/h1\u003e \u003cp\u003e \u003cimg\u003e` should be displayed in the HTML response as `\u0026#x3c;h1\u0026#x3e; just a test \u0026#x3c;/h1\u0026#x3e; \u0026#x3c;p\u0026#x3e; \u0026#x3c;img\u0026#x3e;`.", "id": "GHSA-x82r-6j37-vrgg", "modified": "2025-04-08T14:51:41Z", "published": "2025-04-08T14:51:41Z", "references": [ { "type": "WEB", "url": "https://github.com/pimcore/admin-ui-classic-bundle/security/advisories/GHSA-x82r-6j37-vrgg" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-30166" }, { "type": "WEB", "url": "https://github.com/pimcore/admin-ui-classic-bundle/commit/76b690d4f8fcd9c9d41766bc5238c2513242e60e" }, { "type": "PACKAGE", "url": "https://github.com/pimcore/admin-ui-classic-bundle" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N", "type": "CVSS_V4" } ], "summary": "Pimcore\u0027s Admin Classic Bundle allows HTML Injection" }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.