Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-45532 – Path Traversal / Arbitrary File Read – DataEase before 2.10.23

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-45532 is a path traversal vulnerability in DataEase, an open-source business intelligence and data visualization platform, affecting all versions prior to 2.10.23. The flaw allows an unauthenticated, network-based attacker to read arbitrary files from the underlying server via a crafted request to a static resource endpoint. It carries a HIGH severity rating with a CVSS v4.0 base score of 8.7.

Technical details

  • Root cause: the vulnerable code paths, StaticResourceServer#findResourceAsBase64 and StaticResourceUtils#getImgFileToBase64, sanitize input by filtering only forward-slash (/) characters before resolving a file path.
  • On Windows deployments, the file separator is a backslash (“), which is not filtered, allowing directory-traversal sequences such as ......Windowswin.ini to bypass the restriction.
  • Attack vector: a POST request to /de2api/staticResource/findResourceAsBase64 with a backslash-based traversal payload in the requested resource name.
  • Impact: arbitrary file read on the host filesystem, with contents returned to the attacker as base64-encoded data. No authentication or user interaction is required, and no impact on integrity or availability is noted.

Affected software

  • DataEase (io.dataease) versions prior to 2.10.23, on Windows-hosted deployments where the backslash file separator applies.

Severity

  • CVSS v4.0 Base Score: 8.7 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade DataEase to version 2.10.23 or later, which fixes the incomplete path-separator filtering.
  • If immediate patching is not possible: restrict or monitor network access to the /de2api/staticResource/findResourceAsBase64 endpoint, and avoid running DataEase on Windows hosts until patched; no other vendor-documented workaround exists.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: DataEase
  • Raw response body: DataEase doesn't work properly

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge