CVE-2016-15037: A vulnerability, which was classified as problematic, has been found in go4rayyan Scumblr up to 2.0.1a

Q: How do I fix CVE-2016-15037?

scumblr: upgrade to 2.0.2. Exact commands for each OS are on this page.

Q: Is CVE-2016-15037 being exploited?

CVE-2016-15037 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2016-15037 affect?

CVE-2016-15037 affects scumblr. Severity is low (CVSS 2.4). 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

Q: How urgent is CVE-2016-15037?

Priority 20/100. No elevated risk signals yet.

Routine

LOW 2.4UPGRADE

CVE-2016-15037 is a low-severity flaw (CVSS 2.4) affecting scumblr. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 componen

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	2.4 (Low)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	Required
EPSS exploit chance	0.6% (top 52%)
CISA exploited list	No
Weakness	CWE-79
Published	2024-01-21
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: go4rayyan

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-01-21 06:15 UTCPublished CVE record published
2026-06-17 00:41 UTCUpdated Record last modified

go4rayyan scumblr UPGRADE

Affected: < 2.0.2

Fixed in: 2.0.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy scumblr || rpm -q scumblr || scumblr --version

2. UPGRADE to 2.0.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade scumblr

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade scumblr

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-15037?

scumblr: upgrade to 2.0.2. Exact commands for each OS are on this page.

Is CVE-2016-15037 being exploited?

CVE-2016-15037 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-15037 affect?

CVE-2016-15037 affects scumblr. Severity is low (CVSS 2.4). 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

How urgent is CVE-2016-15037?

Priority 20/100. No elevated risk signals yet.

References

← Back to latest CVEs