Skip to main content
CVE-2025-57795VulnerabilityPublished

CVE-2025-57795: Explorance Blue · Unrestricted File Upload

Affects Explorance BlueSource CVE Database V5

0

Not known to be exploited · CVSS 9.9 Critical : upgrade to 8.14.13 as a priority.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Jan 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 Explorance Blue to 8.14.13.

Affected software

ProductAffectedFixed in
ExploranceBlueAffected
  • <8.14.13
Fixed in
  • 8.14.13

AI-suggested

To mitigate CVE-2025-57795, European organizations should take the following specific actions: 1) Immediately identify and inventory all instances of Explorance Blue in use and verify their versions. 2) Upgrade all affected instances to version 8.14.13 or later once the patch is available. 3) In the interim, restrict file upload functionality by implementing strict server-side validation to allow only safe file types and reject any potentially dangerous files. 4) Enforce strong authentication mechanisms, including multi-factor authentication (MFA), to reduce the risk of credential compromise. 5) Limit user permissions to the minimum necessary to reduce the number of users who can upload files. 6) Monitor logs and file upload directories for unusual activity or unexpected file types. 7) Conduct regular security assessments and penetration testing focused on file upload components. 8) Educate users about the risks of credential sharing and phishing attacks that could lead to account compromise. 9) Employ network segmentation to isolate the application server from critical infrastructure. 10) Prepare incident response plans specifically addressing potential exploitation of this vulnerability.

Description

Explorance Blue versions prior to 8.14.13 contain an authenticated remote file download vulnerability in a web service component. In default configurations, this flaw can be leveraged to achieve remote code execution.

References

Community reviews

Loading reviews…