CVE-2025-56819
An issue in Datart v.1.0.0-rc.3 allows a remote attacker to execute arbitrary code via the INIT connection parameter.
First public PoC
13 hafter publication · 24 Sep 2025
Public PoCs21 on GitHub · 1 Exploit-DB, Metasploit or nuclei
CVSS9.8critical · scored by CISA ADP · CWE-78
CISA KEV
Not listednot known exploited
Timeline
Days relative to CVE publicationFirst public PoC 13 h after publication; not in CISA KEV. First PoC: xyyzxc/CVE-2025-56819 (created 24 Sep 2025, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| xyyzxc/CVE-2025-56819 | 24 Sep 2025 +13 h | 2 | PoC via PoC Index |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: Datart v1.0.0-rc.3 - Remote Code Execution | 15 Oct 2025 | 14 Nov 2026 |
PoC characteristics
What to hunt for in your logs · from 1 PoC repoPOST /api/v1/data-provider/test
- Body markers
"name":"jdbc-data-provider""type":"JDBC""properties""dbType":"H2""url""user""password""driverClass":"org.h2.Driver""serverAggregate""enableSpecialSQL""enableSyncSchemas""syncInterval":"60"inapplication/json- Ports
- 8080
- Seen in
- 1 repo: xyyzxc/CVE-2025-56819
- Evidence
- xyyzxc/CVE-2025-56819/README.md:5
Regex
Generated from PoC characteristics; not yet reviewed. Matches the request path and query.
POST /api/v1/data-provider/test
(?i)^/api/v1/data-provider/test(?:[?#].*)?$
Suricata
Template generated from PoC characteristics. Review before deploying.
POST /api/v1/data-provider/test
alert http any any -> $HOME_NET [8080] (msg:"GG PoC-Monitor CVE-2025-56819 CVE-2025-56819 exploit attempt"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/v1/data-provider/test"; http.request_body; content:"|22|name|22|:|22|jdbc-data-provider|22|"; http.request_body; content:"|22|type|22|:|22|JDBC|22|"; http.request_body; content:"|22|properties|22|"; http.request_body; content:"|22|dbType|22|:|22|H2|22|"; http.request_body; content:"|22|url|22|"; http.request_body; content:"|22|user|22|"; http.request_body; content:"|22|password|22|"; http.request_body; content:"|22|driverClass|22|:|22|org.h2.Driver|22|"; http.request_body; content:"|22|serverAggregate|22|"; http.request_body; content:"|22|enableSpecialSQL|22|"; http.request_body; content:"|22|enableSyncSchemas|22|"; http.request_body; content:"|22|syncInterval|22|:|22|60|22|"; reference:url,poc.griffinguard.io/cve/CVE-2025-56819; classtype:web-application-attack; sid:9632820; rev:1;)
Sigma
Template generated from PoC characteristics. Review before deploying.
POST /api/v1/data-provider/test
title: CVE-2025-56819 exploit attempt (CVE-2025-56819)
id: gg-pocmon-cve-2025-56819-9632820
status: experimental
description: Request pattern taken from public PoCs for CVE-2025-56819. Generated, not reviewed.
references:
- https://poc.griffinguard.io/cve/CVE-2025-56819
logsource:
category: webserver
detection:
selection:
cs-method: POST
cs-uri-stem|contains|all:
- '/api/v1/data-provider/test'
condition: selection
falsepositives:
- Authorized vulnerability scanning
level: critical
tags:
- attack.initial_access
- attack.t1190
- cve.2025.56819