CVE-2016-15037

LOWNVD 2.42.4—
EchelonGraph scoreMEDIUM confidence

Score 2.4 from GitHub Security Advisory (severity: LOW) published 2024-01-21. NVD baseline CVSS 2.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
2.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 2.4Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

A vulnerability, which was classified as problematic, has been found in go4rayyan Scumblr up to 2.0.1a. Affected by this issue is some unknown functionality of the component Task Handler. The manipulation leads to cross site scripting. The attack may be launched remotely. Upgrading to version 2.0.2 is able to address this issue. The patch is identified as 5c9120f2362ddb7cbe48f2c4620715adddc4ee35. It is recommended to upgrade the affected component. VDB-251570 is the identifier assigned to this vulnerability.

CVSS v3
2.4
EG Score
2.4LOWmedium confidence
EG Risk
11
EG Risk 11/100CISA SSVC

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
Severity24% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.6%
EPSS %ILE
46th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

January 21, 2024

Last Modified

November 21, 2024

References (8)

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 152 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2016-15037?
CVE-2016-15037 is a low vulnerability published on January 21, 2024. A vulnerability, which was classified as problematic, has been found in go4rayyan Scumblr up to 2.0.1a. Affected by this issue is some unknown functionality of the component Task Handler. The manipulation leads to cross site scripting. The attack may be launched remotely. Upgrading to version 2.0.2…
When was CVE-2016-15037 disclosed?
CVE-2016-15037 was first published on January 21, 2024, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-15037 actively exploited?
CVE-2016-15037 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2016-15037?
CVE-2016-15037 has a CVSS v3 base score of 2.4 (NVD).
How do I remediate CVE-2016-15037?
A fix for CVE-2016-15037 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2016-15037

Explore →

Is Your Infrastructure Affected by CVE-2016-15037?

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

Book a Demo →Browse All CVEs