Advisory record · GHSA-gp95-j463-vv28

phpMyFAQ: Default Empty API Token Authentication Bypass

CVSS 8.7 HighEPSS 0.0048 · 41st percentile

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

PackageEcosystemAffectedFixed in
thorsten/phpmyfaqPackagist<4.1.34.1.3
phpmyfaq/phpmyfaqPackagist<4.1.34.1.3
Identifiers
GHSA-gp95-j463-vv28 · CVE-2026-35672 · PKSA-jk8b-rmby-gztg · PKSA-xr26-9czp-vbgk
Weakness (CWE)
CWE-1188
Published
20 May 2026
Updated
10 Sept 2026

Machine-written summary

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

Packages thorsten/phpmyfaq and phpmyfaq/phpmyfaq before 4.1.3 are affected, and the fix is in 4.1.3. The REST API's write endpoints for FAQs, categories and questions accept requests with an empty API token header when the administrator has not set a non-empty API client token, which is the default after installation. An unauthenticated attacker on the network could create and modify this content, which the source describes as enabling injected or spam entries. Upgrade to phpMyFAQ 4.1.3 or later.

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.7 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0048, the 41st percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

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