> CVE-2026-46359 [HIGH]

« BACK_TO_HOME
PUBLISHED
2026-05-15 19:17
MODIFIED
2026-05-15 19:17
CVSS_SCORE V3
7.5
EPSS (Prob. Exploit)
0.36%
Top 71.6%
DATA SOURCES:
NVD 🔗 2026-05-15 CWE MITRE 🔗 2026-11-01 FIRST EPSS 🔗 2026-10-25 GITHUB 🔗 2026-11-05 OSV 🔗 2026-07-26

> DESCRIPTION

phpMyFAQ before 4.1.2 contains a sql injection vulnerability in CurrentUser::setTokenData that allows authenticated attackers to execute arbitrary SQL by injecting malicious OAuth token claims. Attackers with Azure AD accounts containing SQL metacharacters in display names or JWT claims can break out of string literals and execute arbitrary database queries.

> AFFECTED_PRODUCTS

ℹ️ Aucun produit affecté n'a encore été publié par NVD pour cette CVE.

> CVSS V3 METRICS

CVSS_VECTOR
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
EXPLOITABILITY
1.6
IMPACT
5.9

> MÉTRIQUES CVSS DÉTAILLÉES

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Métrique Valeur Interprétation
AV (Vecteur d'Attaque)
Attack Vector
Network (N)
Exploit possible à distance via réseau (HTTP, API, etc.)
AC (Complexité d'Attaque)
Attack Complexity
High (H)
Conditions spécifiques doivent être réunies pour exploiter
PR (Privilèges Requis)
Privileges Required
None (N)
Aucune authentification requise
UI (Interaction Utilisateur)
User Interaction
Required (R)
Nécessite une action utilisateur (clic lien, ouverture fichier, etc.)
S (Périmètre)
Scope
Unchanged (U)
Impact reste dans le périmètre du composant compromis
C (Impact Confidentialité)
Confidentiality Impact
High (H)
Divulgation totale d'informations
I (Impact Intégrité)
Integrity Impact
High (H)
Modification totale des données possible
A (Impact Disponibilité)
Availability Impact
High (H)
Interruption totale du service possible

> RÉSUMÉ DES IMPACTS

Confidentialité
High
Divulgation totale d'informations
Intégrité
High
Modification totale des données possible
Disponibilité
High
Interruption totale du service possible

> WEAKNESSES

CWE-89

> CWE DETAILED DESCRIPTIONS

CWE-89: Improper Neutralization of Special Elements used in an SQL Command - The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

> GITHUB SECURITY ADVISORY

GHSA-pm8c-3qq3-72w7 HIGH

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

AFFECTED PACKAGES:
COMPOSER / phpmyfaq/phpmyfaq
<= 4.1.1
Fixed in: 4.1.2
COMPOSER / thorsten/phpmyfaq
<= 4.1.1
Fixed in: 4.1.2

> OSV (GOOGLE OPEN SOURCE VULNERABILITIES)

phpMyFAQ - SQL Injection in CurrentUser::setTokenData via Unescaped OAuth Token Fields

AFFECTED PACKAGES:
Unknown / Unknown
1425 versions affected
ALIASES:
GHSA-pm8c-3qq3-72w7

> HISTORIQUE DES MODIFICATIONS

Première apparition
15/05/2026 19:17
Source: NVD
📊 ENRICHISSEMENT 01/11/2026 06:59
CWE
Champ modifié: Description CWE
Ancienne valeur:
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') - The product constructs all or part of an SQL command using externally-influenced input from an upstream c...
Nouvelle valeur:
CWE-89: Improper Neutralization of Special Elements used in an SQL Command - The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it d...
📊 ENRICHISSEMENT 01/06/2026 06:01
CWE
Champ modifié: Description CWE
Ancienne valeur:
N/A
Nouvelle valeur:
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') - The product constructs all or part of an SQL command using externally-influenced input from an upstream c...
Total des modifications: 2 Dernière mise à jour: 6 days ago

> REFERENCES

https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-pm8c-3qq3-72w7
https://www.vulncheck.com/advisories/phpmyfaq-sql-injection-in-currentuser-setto...
« BACK_TO_HOME