Phishing email creation via unencoded first names
Published Mar 28, 2025 · Updated Apr 1, 2025
HTML injection in Leantime 3.2.1 and earlier allows remote authenticated users to create phishing emails via crafted first names. The processMentions() method inserts the notification author's firstname into email content without HTML encoding, causing attacker-controlled tags to render in messages. A valid account is required, and the demonstrated consequence is attacker-controlled HTML in email sent from the instance's address.
Summary
What happened
HTML injection in Leantime 3.2.1 and earlier allows remote authenticated users to create phishing emails via crafted first names. The processMentions() method inserts the notification author's firstname into email content without HTML encoding, causing attacker-controlled tags to render in messages. A valid account is required, and the demonstrated consequence is attacker-controlled HTML in email sent from the instance's address.
The record
- CVE
- CVE-2025-28254
- Published
- Mar 28, 2025
- Updated
- Apr 1, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-74, CWE-79, T1566
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 28, 2025CVE publishedPublication date reported by the CVE source.
- Apr 1, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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