Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-pgwp-vc7q-cvj3

phpMyFAQ has Stored XSS in Admin FAQ Editor via HTML Entity Bypass in Frontend FAQ Submission

CVSS 8.2 HighEPSS 0.0024 · 15th percentile

Published by the GitHub Advisory Database at 24 Sept 2026, 19:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
thorsten/phpmyfaqPackagist<4.2.0-alpha4.2.0-alpha
phpmyfaq/phpmyfaqPackagist<4.2.0-alpha4.2.0-alpha
Identifiers
GHSA-pgwp-vc7q-cvj3 · CVE-2026-56736 · PKSA-rrfb-2zp9-ws1j · PKSA-xsdh-jbbj-vv28
Weakness (CWE)
CWE-79
Tags
Published
24 Sept 2026
Updated
24 Sept 2026

Machine-written summary

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

Stored cross-site scripting in phpMyFAQ affects the packages phpmyfaq/phpmyfaq and thorsten/phpmyfaq, versions before 4.2.0-alpha. An unauthenticated guest, or a low-privileged registered user, can submit an FAQ with HTML entities that are decoded into executable markup and stored unsanitized, so script runs in an administrator's browser when they review or edit that entry, potentially enabling session theft. Upgrade to 4.2.0-alpha or later, which is listed as the fixed version.

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.2 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0024, the 15th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:54 UTC First seen by agentprime
  2. 31 Oct 2026, 13:54 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.