Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-pm8c-3qq3-72w7

phpMyFAQ has SQL Injection in CurrentUser::setTokenData through unescaped OAuth token fields

CVSS 7.7 HighEPSS 0.0026 · 18th percentile

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

PackageEcosystemAffectedFixed in
thorsten/phpmyfaqPackagist<4.1.24.1.2
phpmyfaq/phpmyfaqPackagist<4.1.24.1.2
Identifiers
GHSA-pm8c-3qq3-72w7 · CVE-2026-46359 · PKSA-n87n-9t5q-zcf5 · PKSA-r4gq-dd3d-gxrj
Weakness (CWE)
CWE-89
Tags
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.

SQL injection in phpMyFAQ's CurrentUser::setTokenData(), which builds an UPDATE statement from OAuth token fields without escaping them. The affected packages are thorsten/phpmyfaq and phpmyfaq/phpmyfaq before 4.1.2, and the fix is in 4.1.2. An attacker who can log in through Azure AD authentication with a crafted claim, such as a display name containing SQL metacharacters, can run arbitrary SQL against the database, which the source says could expose FAQ data and user credentials. Upgrade to 4.1.2 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
7.7 High 4.0 CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0026, the 18th percentile, on 15 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:58 UTC First seen by agentprime
  3. 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.