Skip to main content
CVE-2024-50634VulnerabilityPublished Updated

CVE-2024-50634: Watcharr · n/a

Affects WatcharrSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GitHubyamerooo123/Watcharrpkg:github/yamerooo123/WatcharrOther threatsAffected
  • <=1.43.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately upgrade Watcharr to the latest version once a patch addressing CVE-2024-50634 is released. 2. If patches are not yet available, implement network-level access controls to restrict access to the Watcharr service to trusted IP addresses only. 3. Employ Web Application Firewalls (WAFs) with custom rules to detect and block malformed or suspicious JWT tokens. 4. Conduct thorough audits of JWT implementation and token validation logic to ensure robust signature verification and token integrity checks. 5. Enforce strong cryptographic algorithms and secret management for JWT signing keys. 6. Monitor authentication logs for unusual access patterns or repeated failed token validations indicative of exploitation attempts. 7. Educate administrators and users about the risk and encourage immediate reporting of suspicious activity. 8. Consider isolating the Watcharr service in a segmented network zone to limit potential lateral movement if compromised.

Description

A vulnerability in a weak JWT token in Watcharr v1.43.0 and below allows attackers to perform privilege escalation using a crafted JWT token. This vulnerability is not limited to privilege escalation but also affects all functions that require authentication.

References

Community reviews

Loading reviews…