CVE-2026-46367

HIGHNVD 7.67.6
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
7.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.6Exploit: 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 stored cross-site scripting vulnerability in Utils::parseUrl() that allows authenticated users to inject JavaScript via malformed URLs in comments. Attackers can craft URLs with unescaped quotes to inject event handlers, stealing admin session cookies and achieving full application takeover when visitors view affected FAQ pages.

CVSS v3
7.6
EG Score
7.6(medium)
EPSS
11.8%
KEV
Not listed

Published

May 15, 2026

Last Modified

May 28, 2026

Advisory Details (2)

Auto-updated May 16, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Stored XSS via Utils::parseUrl() in comment rendering · Advisory · thorsten/phpMyFAQ · GitHub

https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-9525-27vj-c8r8
generic

phpMyFAQ - Stored XSS via Utils::parseUrl() in Comment Rendering | Advisories | VulnCheck

https://www.vulncheck.com/advisories/phpmyfaq-stored-xss-via-utils-parseurl-in-comment-rendering

Vendor Advisories for CVE-2026-46367(1)

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

Affected Packages

(4 across 1 ecosystem)
Packagist(4)
PackageVulnerable rangeFixed inDependents
phpMyFAQ4.1.2
phpmyfaq/phpmyfaq2.10.0-alpha ... 4.1.1 (170 versions)4.1.2
phpMyFAQ/phpMyFAQ4.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 / 53× 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 111 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:28 UTCEG score recompute
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-27 21:48 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:43 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:29 UTCEG score recompute
  20. 2026-06-15 17:49 UTCEPSS rescore
  21. 2026-06-14 22:24 UTCEG score recompute
  22. 2026-06-14 10:49 UTCEG score recompute
  23. 2026-06-13 23:13 UTCEG score recompute
  24. 2026-06-13 07:23 UTCEG score recompute
  25. 2026-06-12 23:12 UTCEPSS rescore
  26. 2026-06-12 23:12 UTCEPSS rescore
  27. 2026-06-12 19:33 UTCEG score recompute
  28. 2026-06-12 07:59 UTCEG score recompute
  29. 2026-06-11 20:23 UTCEG score recompute
  30. 2026-06-11 14:00 UTCEPSS rescore
  31. 2026-06-11 08:48 UTCEG score recompute
  32. 2026-06-10 22:18 UTCEPSS rescore
  33. 2026-06-10 21:13 UTCEG score recompute
  34. 2026-06-10 13:22 UTCEPSS rescore
  35. 2026-06-10 13:22 UTCEPSS rescore
  36. 2026-06-10 09:38 UTCEG score recompute
  37. 2026-06-09 22:04 UTCEG score recompute
  38. 2026-06-09 10:25 UTCEG score recompute
  39. 2026-06-08 22:50 UTCEG score recompute
  40. 2026-06-08 14:17 UTCEPSS rescore
  41. 2026-06-08 14:17 UTCEPSS rescore
  42. 2026-06-08 11:14 UTCEG score recompute
  43. 2026-06-07 23:39 UTCEG score recompute
  44. 2026-06-07 15:25 UTCEPSS rescore
  45. 2026-06-07 15:25 UTCEPSS rescore
  46. 2026-06-07 12:04 UTCEG score recompute
  47. 2026-06-07 00:30 UTCEG score recompute
  48. 2026-06-06 13:47 UTCEPSS rescore
  49. 2026-06-06 13:47 UTCEPSS rescore
  50. 2026-06-06 12:55 UTCEG score recompute
  51. 2026-06-06 01:19 UTCEG score recompute
  52. 2026-06-05 22:47 UTCEPSS rescore
  53. 2026-06-05 13:45 UTCEG score recompute
  54. 2026-06-05 06:10 UTCEPSS rescore
  55. 2026-06-05 06:10 UTCEPSS rescore
  56. 2026-06-05 02:10 UTCEG score recompute
  57. 2026-06-04 14:35 UTCEG score recompute
  58. 2026-06-04 13:12 UTCEPSS rescore
  59. 2026-06-04 13:12 UTCEPSS rescore
  60. 2026-06-04 03:00 UTCEG score recompute
  61. 2026-06-03 15:25 UTCEG score recompute
  62. 2026-06-03 03:50 UTCEG score recompute
  63. 2026-06-02 20:13 UTCEPSS rescore
  64. 2026-06-02 16:15 UTCEG score recompute
  65. 2026-06-02 04:40 UTCEG score recompute
  66. 2026-06-01 17:05 UTCEG score recompute
  67. 2026-06-01 13:52 UTCEPSS rescore
  68. 2026-06-01 13:52 UTCEPSS rescore
  69. 2026-06-01 05:30 UTCEG score recompute
  70. 2026-05-31 22:30 UTCEPSS rescore
  71. 2026-05-31 22:30 UTCEPSS rescore
  72. 2026-05-31 00:16 UTCEPSS rescore
  73. 2026-05-31 00:16 UTCEPSS rescore
  74. 2026-05-29 13:44 UTCEPSS rescore
  75. 2026-05-29 13:44 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-46367?
CVE-2026-46367 is a high vulnerability published on May 15, 2026. phpMyFAQ before 4.1.2 contains a stored cross-site scripting vulnerability in Utils::parseUrl() that allows authenticated users to inject JavaScript via malformed URLs in comments. Attackers can craft URLs with unescaped quotes to inject event handlers, stealing admin session cookies and achieving…
When was CVE-2026-46367 disclosed?
CVE-2026-46367 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-46367 actively exploited?
CVE-2026-46367 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 11.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46367?
CVE-2026-46367 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-46367?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46367, 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-46367

Explore →

Is Your Infrastructure Affected by CVE-2026-46367?

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