Phishing via unescaped email display name
Published Apr 7, 2026 · Updated Apr 7, 2026
HTML injection in Papra before 26.4.0 allows remote authenticated users to alter transactional email bodies through a crafted display name. The auth.emails.services.ts templates interpolate user.name directly into verification and password-reset HTML without escaping or sanitization. Registration with a crafted name and configured email delivery are required; resulting messages can replace legitimate links with phishing content from the deployment's trusted sender.
Summary
What happened
HTML injection in Papra before 26.4.0 allows remote authenticated users to alter transactional email bodies through a crafted display name. The auth.emails.services.ts templates interpolate user.name directly into verification and password-reset HTML without escaping or sanitization. Registration with a crafted name and configured email delivery are required; resulting messages can replace legitimate links with phishing content from the deployment's trusted sender.
The record
- CVE
- CVE-2026-35460
- Published
- Apr 7, 2026
- Updated
- Apr 7, 2026
- Vendor
- Papra
- Product
- Papra
- Classifications
- CWE-80, CWE-79, T1566.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 7, 2026CVE publishedPublication date reported by the CVE source.
- Apr 7, 2026Record 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=< 26.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- GitHub advisory transactional-email HTML injection PoCproof of concept · demonstrated
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