CVE-2026-46367: phpMyFAQ has stored XSS via Utils::parseUrl() in comment rendering

high Affects phpmyfaq/phpmyfaq, thorsten/phpmyfaq. Feed 2026.10.29.1, updated 2026-10-28; published 2026-05-06; advisory modified 2026-09-10.

phpMyFAQ has stored XSS via Utils::parseUrl() in comment rendering

Package: phpmyfaq/phpmyfaq Composer
Affected versions: >=4.1.1 and <4.1.2
Fixed in: 4.1.2
Severity: high CVSS 7.6
Exploitation: not on CISA KEV · EPSS 0% (16.2th percentile)
Published: 2026-05-06
Source: osv.dev

References

phpMyFAQ has stored XSS via Utils::parseUrl() in comment rendering

Package: thorsten/phpmyfaq Composer
Affected versions: >=4.1.1 and <4.1.2
Fixed in: 4.1.2
Severity: high CVSS 7.6
Exploitation: not on CISA KEV · EPSS 0% (16.2th percentile)
Published: 2026-05-06
Source: osv.dev

References

CWE-116 CWE-79

NVD record phpmyfaq/phpmyfaq advisories thorsten/phpmyfaq advisories

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs How findings are ranked

Related advisories

CVE-2026-24421 medium phpMyFAQ: /api/setup/backup accessible to any authenticated user (authz missing) same package: phpmyfaq/phpmyfaq
CVE-2026-46364 critical phpMyFAQ has unauthenticated SQL injection via User-Agent header in BuiltinCaptcha same package: phpmyfaq/phpmyfaq
CVE-2024-28105 high phpMyFAQ's File Upload Bypass at Category Image Leads to RCE same package: phpmyfaq/phpmyfaq
CVE-2022-3608 high phpMyFAQ vulnerable to Cross-site Scripting same package: phpmyfaq/phpmyfaq
CVE-2024-27299 high phpMyFAQ SQL Injection at "Save News" same package: phpmyfaq/phpmyfaq
CVE-2024-28107 high phpMyFAQ SQL injections at insertentry & saveentry same package: phpmyfaq/phpmyfaq