CVE-2026-46360

MEDIUMNVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

Score 5.4 from GitHub Security Advisory published 2026-05-15. NVD baseline CVSS 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
5.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.4Exploit: 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 SvgSanitizer::decodeAllEntities() that limits recursive entity decoding to 5 iterations, allowing attackers to bypass sanitization. Authenticated users with FAQ_EDIT permission can upload malicious SVG files with deeply nested ampersand encoding around numeric HTML entities to reconstruct javascript: URLs, which execute arbitrary JavaScript when clicked by other users viewing the uploaded SVG.

CVSS v3
5.4
EG Score
5.4(medium)
EPSS
4.9%
KEV
Not listed

Published

May 15, 2026

Last Modified

May 28, 2026

Advisory Details (2)

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

SVG Sanitizer Entity Decoding Depth Limit Bypass Leading to Stored XSS · Advisory · thorsten/phpMyFAQ · GitHub

https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-whqh-9pq5-c7r3
generic

phpMyFAQ - Stored XSS via Entity Decoding Depth Limit Bypass in SVG Sanitizer | Advisories | VulnCheck

https://www.vulncheck.com/advisories/phpmyfaq-stored-xss-via-entity-decoding-depth-limit-bypass-in-svg-sanitizer

Vendor Advisories for CVE-2026-46360(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
phpmyfaq/phpmyfaq2.10.0-alpha ... 4.1.1 (170 versions)4.1.2—
phpMyFAQ/phpMyFAQ—4.1.2—
thorsten/phpmyfaq2.10.0-alpha ... 4.1.1 (170 versions)4.1.2—
thorsten/phpMyFAQ—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 / 47× 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.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-46360?
CVE-2026-46360 is a medium vulnerability published on May 15, 2026. phpMyFAQ before 4.1.2 contains a stored cross-site scripting vulnerability in SvgSanitizer::decodeAllEntities() that limits recursive entity decoding to 5 iterations, allowing attackers to bypass sanitization. Authenticated users with FAQ_EDIT permission can upload malicious SVG files with deeply…
When was CVE-2026-46360 disclosed?
CVE-2026-46360 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-46360 actively exploited?
CVE-2026-46360 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46360?
CVE-2026-46360 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-46360?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46360, 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-46360

Explore →

Is Your Infrastructure Affected by CVE-2026-46360?

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

Start Free Scan →Browse All CVEs