Extension "Mail" vulnerabilities and CVEs
Known vulnerabilities affecting Extension "Mail", with exploit availability attached to each one, so you can tell a flaw someone has written code for from one nobody has.
6 vulnerabilities tracked.
- 7.1 Backend actions and ajax routes of the mail module do not check whether the backend user has access to the page of the requested mail or…
- 6.9 The click tracking middleware does not validate the authentication code of a recipient if the code is omitted.
- 5.3 The click tracking middleware accepts an arbitrary target URL and redirects to it.
- 5.3 Saving the configuration of the mail backend module writes submitted settings to the page TSconfig without restricting them to the…
- 5.3 Content of external URL mails, their stylesheets and images to embed is fetched by the server without validating the target host.
- 5.1 The HTML content of mails and tracked URLs are rendered unescaped in the backend module.
What this covers
This feed accumulates forward from the day it started storing records, and a name search that finds nothing here is also looked up against the registers directly — so an older advisory resolves even when it predates the corpus. It is still a reading view, not a substitute for the vendor's own advisory, and absence from this page is not a statement that Extension "Mail" is free of vulnerabilities.
Query this from an agent over MCP · Check a lockfile by version
Other products tracked here
Chrome Zephyr Android macOS Windows Server 2022 Windows 11 version 26H1 Windows 11 Version 24H2 Windows Server 2025 (Server Core installation) Windows 11 Version 25H2 Windows Server 2025 Windows Server 2019 Windows Server 2019 (Server Core installation) Windows 10 Version 21H2 Windows 10 Version 1809 Windows 10 Version 22H2 Red Hat Enterprise Linux 9 Windows Server 2016 (Server Core installation) Windows Server 2016 Windows 10 Version 1607 Windows Server 2012 R2 (Server Core installation) Windows Server 2012 R2 n/a Red Hat Enterprise Linux 10 Windows Server 2012