Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| # | POC Description | Source Link | Shenlong Link |
|---|---|---|---|
| 1 | https://github.com/vulhub/vulhub/blob/master/dataease/CVE-2025-49001/README.md | POC Details | |
| 2 | None | https://github.com/Threekiii/Awesome-POC/blob/master/Web%E5%BA%94%E7%94%A8%E6%BC%8F%E6%B4%9E/DataEase%20JWT%20%E8%AE%A4%E8%AF%81%E7%BB%95%E8%BF%87%E6%BC%8F%E6%B4%9E%20CVE-2025-49001.md | POC Details |
| 3 | DataEase < 2.10.10 contains a broken authentication caused by ineffective secret verification, letting users forge JWT tokens, exploit requires no special privileges. | https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2025/CVE-2025-49001.yaml | POC Details |
No public POC found.
Login to generate AI POC| CVE-2025-48998 | Dataease MYSQL JDBC File Reading Vulnerability | |
| CVE-2025-48999 | Dataease Redshift Data Source JDBC Connection Parameters Not Verified Leads to RCE Vulnera | |
| CVE-2025-49002 | Dataease H2 Database Remote Code Execution (RCE) Bypass Vulnerability |
No comments yet