Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2026-46359— phpMyFAQ - SQL Injection in CurrentUser::setTokenData via Unescaped OAuth Token Fields

CVSS 7.5 · High
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2026-46359

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
phpMyFAQ - SQL Injection in CurrentUser::setTokenData via Unescaped OAuth Token Fields
Source: NVD (National Vulnerability Database)
Vulnerability 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.
Source: NVD (National Vulnerability Database)
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Source: NVD (National Vulnerability Database)
Vulnerability Type
SQL命令中使用的特殊元素转义处理不恰当(SQL注入)
Source: NVD (National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
thorstenphpmyfaq 0 ~ 4.1.2 -

II. Public POCs for CVE-2026-46359

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-46359

登录查看更多情报信息。

Same Patch Batch · thorsten · 2026-05-15 · 13 CVEs total

CVE-2026-463649.8 CRITICALphpMyFAQ - SQL Injection via User-Agent Header in BuiltinCaptcha
CVE-2026-450109.1 CRITICALphpMyFAQ - Unauthenticated Two-Factor Authentication Brute-Force via /admin/check Endpoint
CVE-2026-463677.6 HIGHphpMyFAQ - Stored XSS via Utils::parseUrl() in Comment Rendering
CVE-2026-463667.5 HIGHphpMyFAQ - Unauthenticated Information Disclosure via getIdFromSolutionId Permission Bypas
CVE-2026-463616.9 MEDIUMphpMyFAQ - Stored Cross-Site Scripting via raw Filter in search.twig
CVE-2026-450086.5 MEDIUMphpMyFAQ - Path Traversal in Client::deleteClientFolder via URL Parameter
CVE-2026-463626.5 MEDIUMphpMyFAQ - Authorization Bypass in Admin Pages via Non-Terminating Permission Check
CVE-2026-463605.4 MEDIUMphpMyFAQ - Stored XSS via Entity Decoding Depth Limit Bypass in SVG Sanitizer
CVE-2026-463635.4 MEDIUMphpMyFAQ - Stored XSS in FAQ Question/Answer via Encode-Decode Bypass
CVE-2026-463655.4 MEDIUMphpMyFAQ - Missing Authorization in Tag Deletion Endpoint
CVE-2026-450074.3 MEDIUMphpMyFAQ - Missing Permission Check on 12 Configuration API Endpoints Allows Information D
CVE-2026-450094.3 MEDIUMphpMyFAQ - Insufficient Authorization Check in Admin API Endpoints

IV. Related Vulnerabilities

V. Comments for CVE-2026-46359

No comments yet


Leave a comment