High (8.8)

CVE-2025-70828: [PoC]

CVE-2025-70828

An issue in Datart v1.0.0-rc.3 allows attackers to execute arbitrary code via the url parameter in the JDBC configuration...

Security Advisory: Critical Code Execution Vulnerability in Datart

Overview

A critical security vulnerability has been identified in Datart, an open-source data visualization and reporting platform. This flaw, tracked as CVE-2025-70828, is present in version 1.0.0-rc.3. It allows an authenticated attacker to execute arbitrary code on the server hosting the Datart application, potentially leading to a complete system compromise.

In simple terms, the vulnerability exists in the feature that allows administrators to configure database connections. A malicious actor can exploit a weakness in how the system processes the database connection URL (url parameter) to inject and run harmful commands directly on the underlying server.

Impact and Severity

This vulnerability has been rated as HIGH severity with a CVSS score of 8.8. The primary risk is Remote Code Execution (RCE).

If successfully exploited, an attacker with administrative access to the Datart application could:

  • Gain full control of the server hosting Datart.
  • Steal, modify, or delete sensitive data from connected databases.
  • Install malware or use the compromised server to launch further attacks on internal networks.
  • Disrupt business operations by shutting down services.

Affected Software

  • Datart v1.0.0-rc.3

All deployments of this specific version are vulnerable.

Remediation and Mitigation

The most effective action is to upgrade immediately. The Datart development team has addressed this issue in subsequent releases.

Primary Action: Upgrade

  1. Immediately upgrade your Datart installation to the latest stable version available. Check the official Datart GitHub repository or release channels for the patched version. Do not continue running the vulnerable release (v1.0.0-rc.3).

Immediate Mitigations (If Upgrade is Delayed): If an immediate upgrade is not possible, implement the following strict access controls to reduce risk:

  1. Restrict Network Access: Ensure the Datart admin interface is not accessible from the public internet. Place it behind a VPN or firewall rules that limit access to only trusted, necessary IP addresses.
  2. Review Admin Credentials: Audit and strengthen credentials for all accounts with administrative privileges within Datart. Enforce strong, unique passwords and consider multi-factor authentication if supported.
  3. Principle of Least Privilege: Review and minimize the number of users who have administrative rights to configure JDBC data sources. Only essential personnel should have this access.
  4. Monitor for Suspicious Activity: Review server and application logs for any unusual configuration changes or unexpected database connection attempts, particularly those with unusual URLs.

Note: These mitigations only reduce the attack surface and are not a substitute for applying the official security update. Upgrading to a patched version is the only way to fully resolve this vulnerability.

Share:

Never miss a critical vulnerability

Get real-time security alerts delivered to your preferred platform.

Public PoC References

Unverified third-party code

These repositories are publicly listed on GitHub and have not been audited by Yazoul Security. They may contain malware, backdoors, destructive payloads, or operational security risks (telemetry, exfiltration). Treat them as hostile binaries. Inspect source before execution. Run only in isolated, disposable lab environments (offline VM, no credentials, no production data).

Authorized use only. This information is provided for defensive research, detection engineering, and patch validation. Using exploit code against systems you do not own or do not have explicit written permission to test is illegal in most jurisdictions and violates Yazoul's terms of use.

Repository Stars
xiaoxiaoranxxx/CVE-2025-70828

Datart v1.0.0-rc.3 JDBC Connection String Injection Leading to Arbitrary File Read

★ 4

Showing 1 of 1 known references. Source: nomi-sec/PoC-in-GitHub.

Related Advisories

Never Miss a Critical Alert

CVE advisories, breach reports, and threat intel — delivered daily to your inbox.