Skip to main content
CVE-2025-55454VulnerabilityPublished Updated

CVE-2025-55454: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

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

What to do

AI-suggested

To mitigate this vulnerability, European organizations should take the following specific actions: 1) Immediately identify and inventory all instances of DooTask v1.0.51 or related versions in their environment. 2) Restrict access to the /msg/sendfiles component to only trusted and necessary users, implementing strict role-based access controls to minimize the number of authenticated users who can upload files. 3) Implement file upload validation and sanitization controls, such as restricting allowed file types, scanning uploaded files with advanced malware detection tools, and enforcing file size limits. 4) Monitor logs and network traffic for unusual file upload activities or execution attempts originating from the DooTask application. 5) If a patch or update becomes available from the vendor, prioritize its deployment. 6) Consider deploying web application firewalls (WAFs) with custom rules to detect and block suspicious file upload attempts targeting this endpoint. 7) Conduct regular security assessments and penetration testing focused on file upload functionalities to identify similar weaknesses. 8) Educate users about the risks of uploading untrusted files and enforce strong authentication mechanisms to reduce the risk of credential compromise.

Description

An authenticated arbitrary file upload vulnerability in the component /msg/sendfiles of DooTask v1.0.51 allows attackers to execute arbitrary code via uploading a crafted file.

References

Community reviews

Loading reviews…