Advisory record · GHSA-9525-27vj-c8r8

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

CVSS 8.3 HighEPSS 0.0025 · 16th percentile

Published by the GitHub Advisory Database at 6 May 2026, 20:10 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
thorsten/phpmyfaqPackagist>=4.1.1, <4.1.24.1.2
phpmyfaq/phpmyfaqPackagist>=4.1.1, <4.1.24.1.2
Identifiers
GHSA-9525-27vj-c8r8 · CVE-2026-46367 · PKSA-1zxw-krpv-74xh · PKSA-vm8f-6283-2vfw
Weakness (CWE)
CWE-79 · CWE-116
Published
6 May 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

This advisory covers a stored cross-site scripting flaw in phpMyFAQ, affecting the Packagist packages thorsten/phpmyfaq and phpmyfaq/phpmyfaq versions 4.1.1 up to but not including 4.1.2. An attacker with any registered account can submit a comment containing a crafted URL that, when rendered with the comment editor enabled, runs attacker-supplied JavaScript in the browsers of visitors, including administrators. The advisory says this could be used to steal admin session cookies. The fix is to upgrade to version 4.1.2.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.3 High 4.0 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 CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0025, the 16th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 15 May 2026, 18:36 UTC Confirmed by the CVE List
  2. 31 Oct 2026, 13:59 UTC First seen by agentprime
  3. 31 Oct 2026, 13:59 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.