Skip to main content
VulnerabilityPublished

CVE-2024-48827: Watcharr · Insufficient Session Expiration

Affects WatcharrSource CVE Database V5

0

Public exploit available (Exploit-DB) · CVSS 8.8 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.7% chance of exploitation in 30 days – higher than 86% 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

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 11 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

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

    Not in CISA KEV and no source reports exploitation

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

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by MITRE Corporation

    , 3 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. First Exploit-DB entry (opens in a new tab)

    Watcharr 1.43.0 - Remote Code Execution (RCE)

    , 177 days after disclosure

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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubsbondco/Watcharrpkg:github/sbondco/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

Until an official patch is released, organizations should implement several specific mitigations: 1) Restrict network access to the Watcharr Change Password function by using firewalls, VPNs, or network segmentation to limit exposure only to trusted administrators. 2) Enforce strong authentication and authorization controls to ensure only legitimate users with appropriate privileges can access password management features. 3) Monitor logs and network traffic for unusual activity related to password changes or attempts to exploit this function. 4) Employ application-layer firewalls or intrusion prevention systems (IPS) with custom rules to detect and block suspicious payloads targeting the Change Password endpoint. 5) Conduct thorough internal audits of user privileges and remove unnecessary access rights to minimize the impact of potential privilege escalation. 6) Prepare incident response plans specifically addressing potential exploitation of this vulnerability, including rapid isolation and forensic analysis. 7) Stay informed through vendor communications and security advisories for the release of patches or updates and prioritize immediate deployment once available. 8) Consider temporary disabling or limiting the Change Password functionality if business operations allow, to reduce attack surface.

Description

An issue in sbondCo Watcharr v.1.43.0 allows a remote attacker to execute arbitrary code and escalate privileges via the Change Password function.

References

Community reviews

Loading reviews…