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.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.5(medium)
EPSS
11.5%
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.
github Patch Available🟡 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 rangeFixed inDependents
phpmyfaq/phpmyfaq2.10.0-alpha ... 4.1.1 (170 versions)4.1.2—
thorsten/phpmyfaq2.10.0-alpha ... 4.1.1 (170 versions)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 / 54× 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 130 total refreshes for this CVE.

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

Related CVEs(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 in the National Vulnerability Database 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 11.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46359, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs