Skip to content
Fencer Vulns
high 7.6

CVE-2026-46367 json

phpMyFAQ - Stored XSS via Utils::parseUrl() in Comment Rendering

published 2026-05-06 6 mo ago modified 2026-11-08 17 h ago also EUVD-2026-30578 , GHSA-9525-27vj-c8r8

cvss
7.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 16%
public exploits
0
none known

Summary

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.

Patch / fix

  • packagist thorsten/phpmyfaq 4.1.2
  • packagist phpmyfaq/phpmyfaq 4.1.2
  • thorsten phpmyfaq 4.1.2

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
5 mo ago

Exploit prediction

0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-9525-27vj-c8r8 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 7.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N
CNA 4.0 8.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N
GitHub 3.1 7.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N
CNA 4.0 8.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
packagist thorsten/phpmyfaq
>=4.1.1, <4.1.2
4.1.2
packagist phpmyfaq/phpmyfaq
>=4.1.1, <4.1.2
4.1.2

Affected products

  • thorsten phpmyfaq

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation
  • CWE-116 Improper Encoding or Escaping of Output

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.