Stored XSS via unsanitized bounce callback errors
Published Aug 30, 2021 · Updated Sep 17, 2024
Stored XSS in Mautic before 3.3.4 and before 4.0.0 allows remote attackers to run JavaScript when a user opens a contact. The unauthenticated bounce-management callback stores the error and error_related_to POST fields without sufficient sanitization and renders them in a lead details page. Execution requires an authenticated user to open the affected contact, after which the payload runs in that user's browser and can read or alter information available to the session.
Summary
What happened
Stored XSS in Mautic before 3.3.4 and before 4.0.0 allows remote attackers to run JavaScript when a user opens a contact. The unauthenticated bounce-management callback stores the error and error_related_to POST fields without sufficient sanitization and renders them in a lead details page. Execution requires an authenticated user to open the affected contact, after which the payload runs in that user's browser and can read or alter information available to the session.
The record
- CVE
- CVE-2021-27910
- Published
- Aug 30, 2021
- Updated
- Sep 17, 2024
- Vendor
- Acquia
- Product
- Mautic
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 30, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <3.3.4
- Affected versionversion=unspecified <4.0.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo