CVE-2026-46359

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-15. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
50
EG Risk 50/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
27th
KEV
Not listed

Published

May 15, 2026

Last Modified

May 28, 2026

Advisory Details (2)

Auto-updated May 18, 2026
🔬 Proof of concept available. Patch available. Sources: github.
githubMentions a patch (unverified)🟡 PoC Available

SQL injection in CurrentUser::setTokenData via unescaped OAuth token fields · Advisory · thorsten/phpMyFAQ · GitHub

https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-pm8c-3qq3-72w7
generic

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

https://www.vulncheck.com/advisories/phpmyfaq-sql-injection-in-currentuser-settokendata-via-unescaped-oauth-token-fields

Vendor Advisories for CVE-2026-46359(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Packagist(2)
PackageVulnerable rangeFix by version rangeDependents
phpmyfaq/phpmyfaq2.10.0-alpha ... 4.1.1 (170 versions)
  • every version up to 4.1.2: fixed in 4.1.2
—
thorsten/phpmyfaq2.10.0-alpha ... 4.1.1 (170 versions)
  • every version up to 4.1.2: fixed in 4.1.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 186 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-30 04:28 UTCOSV refresh
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-27 13:48 UTCEPSS rescore
  13. 2026-09-26 15:59 UTCEPSS rescore
  14. 2026-09-23 17:53 UTCEPSS rescore
  15. 2026-09-20 20:15 UTCEPSS rescore
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-17 19:31 UTCEPSS rescore
  18. 2026-09-16 14:08 UTCEPSS rescore
  19. 2026-09-16 05:15 UTCEPSS rescore
  20. 2026-09-13 16:47 UTCEPSS rescore
  21. 2026-09-12 15:01 UTCEPSS rescore
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-11 09:37 UTCEPSS rescore
  24. 2026-09-11 07:23 UTCOSV refresh
  25. 2026-09-10 09:34 UTCEPSS rescore
Show 75 more
  1. 2026-09-08 22:00 UTCEPSS rescore
  2. 2026-09-07 16:01 UTCEPSS rescore
  3. 2026-09-06 13:47 UTCEPSS rescore
  4. 2026-09-04 05:06 UTCEPSS rescore
  5. 2026-09-02 14:12 UTCEPSS rescore
  6. 2026-09-01 13:54 UTCEPSS rescore
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 01:22 UTCEPSS rescore
  9. 2026-08-28 21:41 UTCEPSS rescore
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-26 14:46 UTCEPSS rescore
  12. 2026-08-25 13:49 UTCEPSS rescore
  13. 2026-08-23 17:27 UTCEG score recompute
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-22 01:29 UTCEG score recompute
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-20 19:23 UTCEG score recompute
  19. 2026-08-19 17:04 UTCEPSS rescore
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-17 10:15 UTCEG score recompute
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 03:48 UTCEG score recompute
  25. 2026-08-16 02:14 UTCEPSS rescore
  26. 2026-08-15 01:30 UTCEPSS rescore
  27. 2026-08-14 02:18 UTCEG score recompute
  28. 2026-08-13 22:00 UTCEPSS rescore
  29. 2026-08-12 14:51 UTCEG score recompute
  30. 2026-08-12 13:51 UTCEPSS rescore
  31. 2026-08-11 13:59 UTCEG score recompute
  32. 2026-08-11 00:47 UTCEG score recompute
  33. 2026-08-11 00:00 UTCEPSS rescore
  34. 2026-08-10 00:13 UTCEG score recompute
  35. 2026-08-09 13:46 UTCEPSS rescore
  36. 2026-08-09 01:45 UTCEG score recompute
  37. 2026-08-08 16:37 UTCEPSS rescore
  38. 2026-08-07 18:48 UTCEG score recompute
  39. 2026-08-06 19:59 UTCEG score recompute
  40. 2026-08-06 13:47 UTCEPSS rescore
  41. 2026-08-05 21:30 UTCEG score recompute
  42. 2026-08-05 19:17 UTCEPSS rescore
  43. 2026-08-04 15:10 UTCEPSS rescore
  44. 2026-08-04 10:39 UTCEPSS rescore
  45. 2026-08-03 18:55 UTCEG score recompute
  46. 2026-08-03 10:36 UTCEPSS rescore
  47. 2026-08-02 07:24 UTCEG score recompute
  48. 2026-08-02 02:27 UTCEPSS rescore
  49. 2026-08-01 18:53 UTCEG score recompute
  50. 2026-08-01 04:16 UTCEPSS rescore
  51. 2026-07-30 16:28 UTCEPSS rescore
  52. 2026-07-30 01:30 UTCEPSS rescore
  53. 2026-07-28 15:36 UTCEPSS rescore
  54. 2026-07-27 14:13 UTCEPSS rescore
  55. 2026-07-26 14:54 UTCEPSS rescore
  56. 2026-07-26 14:54 UTCEPSS rescore
  57. 2026-07-25 14:18 UTCEPSS rescore
  58. 2026-07-24 14:17 UTCEPSS rescore
  59. 2026-07-23 14:18 UTCEPSS rescore
  60. 2026-07-23 03:17 UTCEG score recompute
  61. 2026-07-22 14:08 UTCEPSS rescore
  62. 2026-07-21 15:24 UTCEPSS rescore
  63. 2026-07-20 17:08 UTCEPSS rescore
  64. 2026-07-19 14:31 UTCEPSS rescore
  65. 2026-07-19 02:29 UTCEPSS rescore
  66. 2026-07-18 10:04 UTCEPSS rescore
  67. 2026-07-18 00:59 UTCOSV refresh
  68. 2026-07-16 17:03 UTCEPSS rescore
  69. 2026-07-15 16:57 UTCEPSS rescore
  70. 2026-07-15 02:00 UTCEPSS rescore
  71. 2026-07-13 22:30 UTCEPSS rescore
  72. 2026-07-13 06:13 UTCEPSS rescore
  73. 2026-07-12 05:46 UTCEPSS rescore
  74. 2026-07-11 08:27 UTCEPSS rescore
  75. 2026-07-09 19:10 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-46359?
CVE-2026-46359 is a high vulnerability published on May 15, 2026. 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…
When was CVE-2026-46359 disclosed?
CVE-2026-46359 was first published on May 15, 2026, with the most recent update on May 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46359 actively exploited?
CVE-2026-46359 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46359?
CVE-2026-46359 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-46359?
A fix for CVE-2026-46359 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46359 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46359

Explore →

Is Your Infrastructure Affected by CVE-2026-46359?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs