Skip to main content
CVE-2026-25925VulnerabilityPublished Updated

CVE-2026-25925: modery PowerDocu · Deserialization of Untrusted Data

Affects modery PowerDocuSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High : upgrade to 2.4.0 soon.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Feb 2026

  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-25.

What to do

Upgrade modery PowerDocu to 2.4.0.

Affected software

ProductAffectedFixed in
moderyPowerDocuAffected
  • <2.4.0
Fixed in
  • 2.4.0

AI-suggested

1. Upgrade PowerDocu to version 2.4.0 or later immediately to apply the official patch addressing this vulnerability. 2. Implement strict validation and sanitization of all JSON files imported into PowerDocu, especially those containing the $type property, to prevent unsafe deserialization. 3. Restrict the sources from which JSON files can be loaded, limiting to trusted and verified origins only. 4. Educate users about the risks of opening untrusted or unsolicited JSON files and implement policies to reduce the risk of social engineering attacks. 5. Employ application whitelisting and endpoint detection and response (EDR) solutions to monitor and block suspicious process behaviors indicative of deserialization attacks. 6. Regularly audit and monitor logs for unusual activity related to PowerDocu usage, particularly file imports and execution events. 7. Consider isolating PowerDocu usage in sandboxed or virtualized environments to contain potential exploitation. 8. Coordinate with IT security teams to integrate vulnerability management processes ensuring timely updates and risk assessments for third-party software like PowerDocu.

Description

PowerDocu contains a Windows GUI executable to perform technical documentations. Prior to 2.4.0, PowerDocu contains a critical security vulnerability in how it parses JSON files within Flow or App packages. The application blindly trusts the $type property in JSON files, allowing an attacker to instantiate arbitrary .NET objects and execute code. This vulnerability is fixed in 2.4.0.

References

Community reviews

Loading reviews…