CVE-2026-46359

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

Published May 15, 2026 CVSS 4.0 · 7.7 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability resides in phpMyFAQ’s CurrentUser::setTokenData function, where OAuth token claims are not properly escaped. A user who is authenticated can craft token fields containing SQL metacharacters, enabling them to break out of string literals and inject arbitrary SQL statements. This flaw allows attackers to read, modify, or delete data within the application’s database, potentially compromising confidentiality and integrity of stored information.

Affected Systems

Affected systems include installations of thorsten’s phpMyFAQ product prior to version 4.1.2 that are configured to use Azure Active Directory for authentication. Users possessing Azure AD accounts whose display names or JWT claims contain SQL metacharacters can exploit this issue. The vulnerability is limited to systems that process OAuth tokens without proper input sanitization.

Risk and Exploitability

The CVSS score of 7.7 indicates a high severity risk. The exploit requires an authenticated Azure AD account and the ability to embed SQL metacharacters in token fields, which limits the attack surface but still poses significant danger if users with such accounts exist. EPSS score of < 1% indicates a very low probability of exploitation, and the flaw is not listed in the CISA KEV catalog, suggesting it is not currently a known exploited vulnerability. Nonetheless, the potential for arbitrary database access warrants immediate attention.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade phpMyFAQ to version 4.1.2 or later to fix the vulnerable OAuth token handling
  • If an upgrade is not possible, enforce strict validation of OAuth token claims to reject or escape SQL metacharacters before they are stored
  • Disable or reconfigure Azure Active Directory integration until remediation is applied to prevent token-based injection

Generated by OpenCVE AI on May 28, 2026 at 17:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-pm8c-3qq3-72w7 phpMyFAQ has SQL Injection in CurrentUser::setTokenData through unescaped OAuth token fields
History
Type Values Removed Values Added
First Time appeared Phpmyfaq
Phpmyfaq phpmyfaq
CPEs cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*
Vendors & Products Phpmyfaq
Phpmyfaq phpmyfaq
Metrics cvssV4_0

{'score': 7.7, 'vector': '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'}

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Thorsten
Thorsten phpmyfaq
Vendors & Products Thorsten
Thorsten phpmyfaq
Type Values Removed Values Added
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.
Title phpMyFAQ - SQL Injection in CurrentUser::setTokenData via Unescaped OAuth Token Fields
Weaknesses CWE-89
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 8, 2026, 2:03 PM
Reserved
May 13, 2026, 7:40 PM
Status
Deferred
Published
May 15, 2026, 7:17 PM
Modified
Oct 26, 2026, 2:10 PM