Skip to main content
VulnerabilityPublished

CVE-2026-123991: DataEase · Unrestricted Upload

Affects DataEaseSource CVE Database V5

0
Compare

Public exploit available · CVSS 6.9 Medium.

Data as of 7 Nov 2026, 17:05 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulDB)CVSS 4.06.9
CNA (VulDB)CVSS 3.17.3
CNA (VulDB)CVSS 3.07.3
CNA (VulDB)CVSS 2.07.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
DataEaseAffected
  • 2.10.0 – 2.10.27
28 affected builds
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:dataease:dataease:*:*:*:*:*:*:*:*

AI-suggested

Upgrade DataEase to version 2.10.28 or later, where the vulnerability is fixed by enforcing authentication on the static-resource upload endpoint. This is the official vendor fix and the recommended remediation. No additional mitigations are specified or required once the upgrade is applied.

Description

CVE-2026-123991 is a vulnerability in DataEase versions 2.10.0 through 2.10.19 that allows unrestricted file upload via the Authentication Filter component. The flaw exists in the WhitelistUtils.endsWithAny function, which improperly handles file arguments, enabling remote attackers to upload files without restriction. The issue is addressed in DataEase version 2.10.28 by enforcing authentication on the static-resource upload endpoint regardless of URI suffix whitelist.

References

Community reviews

Loading reviews…