Skip to main content
VulnerabilityPublished

CVE-2025-58384: DOXENSE WATCHDOC · Deserialization of Untrusted Data

Source CVE Database V5

0

Not known to be exploited · CVSS 10.0 Critical · fixed in 6.1.1.5332 : patch DOXENSE WATCHDOC as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Affects
DOXENSE WATCHDOC before 6.1.1.5332
Patch
Available – fixed in 6.1.1.5332
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Sep 2025

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

What to do

AI-suggested

  1. Immediate upgrade to DOXENSE WATCHDOC version 6.1.1.5332 or later, where the vulnerability is fixed, is the most effective mitigation.
  2. Restrict network access to the Watchdoc administration interface to trusted internal IP addresses only, using firewalls or network segmentation, to reduce exposure.
  3. Disable or block .NET Remoting communication if not required or replace it with more secure communication protocols.
  4. Implement strict input validation and monitoring on the administration interface to detect anomalous serialized data or unexpected requests.
  5. Employ application-layer firewalls or intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics targeting deserialization attacks.
  6. Conduct regular audits of Watchdoc logs and system behavior to identify suspicious activity indicative of exploitation attempts.
  7. Maintain an incident response plan specifically addressing potential exploitation of monitoring infrastructure. 8.

Description

In DOXENSE WATCHDOC before 6.1.1.5332, Deserialization of Untrusted Data can lead to remote code execution through the .NET Remoting library in the Watchdoc administration interface.

References

Community reviews

Loading reviews…