dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-46359

HIGH · 7.5 CVSS v3.1 Published 2026-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

phpMyFAQ before 4.1.2 has a SQL injection vulnerability in CurrentUser::setTokenData where OAuth token claims (specifically from Azure AD) containing SQL metacharacters in display names or JWT claims are not properly sanitized, allowing authenticated attackers to break out of string literals and execute arbitrary SQL queries.

MitigationUpgrade to phpMyFAQ 4.1.2 or later. Until then, restrict or carefully audit Azure AD user display names to avoid SQL metacharacters, and monitor for suspicious database queries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify phpMyFAQ version
    Locate the version file (typically version.php in the root directory or check admin dashboard footer) and note the version number
    Affected if version is lower than 4.1.2 (e.g., 4.1.0, 4.0.x, 3.x)
  2. Confirm OAuth/Azure AD integration is active
    Examine the phpMyFAQ configuration files (usually in config/ or inc/ directory) for OAuth provider settings, specifically Azure AD / Microsoft Entra ID configuration entries
    Affected if OAuth authentication with Azure AD is configured and enabled in the installation
  3. Locate vulnerable code in CurrentUser class
    Find the file containing the CurrentUser class (typically in inc/ or src/ directory) and inspect the setTokenData method for SQL query construction using token claims
    Affected if the setTokenData method processes OAuth token displayName or JWT claims without parameterized queries or proper escaping
  4. Check database for anomalous SQL patterns
    Review database query logs or enable query logging temporarily to look for unexpected SQL syntax, UNION statements, or SQL comments (--, /*) in user-associated queries originating from OAuth sessions
    Affected if database logs show SQL injection patterns matching OAuth user display names or claims

You are affected if phpMyFAQ version is below 4.1.2 AND OAuth/Azure AD authentication is enabled, allowing SQL injection via malicious display names in token claims.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to phpMyFAQ 4.1.2 or later. Until then, restrict or carefully audit Azure AD user display names to avoid SQL metacharacters, and monitor for suspicious database queries.

Recommended fix Moderate confidence

phpMyFAQ 4.1.2 or later

  1. 1. Back up your current phpMyFAQ installation and database before proceeding with any changes.
  2. 2. Download phpMyFAQ version 4.1.2 or the latest stable release from the official phpMyFAQ repository or website.
  3. 3. Replace the existing phpMyFAQ files with the new version, preserving your configuration and data files.
  4. 4. Verify that the upgrade completed successfully by logging into the admin interface.
  5. 5. If using Azure AD OAuth authentication, test that user authentication still functions correctly with various display name formats.
Caveat Review release notes for any breaking changes between your current version and 4.1.2, particularly regarding OAuth/Azure AD configuration

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46359 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46359 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data