Submit #765097: jeesite 5.15.1 JDBC Connection Injection

Due to the lack of validation on the JDBC URL and driver class name, an attacker can exploit this via:
1. Arbitrary File Read: By specifying the MySQL driver and connecting to an attacker-controlled "Rogue MySQL Server". Utilizing the LOAD DATA LOCAL INFILE feature of the MySQL protocol, the malicious server can request the client (victim server) to read and upload arbitrary local files (e.g., /etc/passwd or C:/Windows/win.ini).
2. Remote Code Execution (RCE): If drivers like H2 Database, SQLite, or a vulnerable MySQL driver (susceptible to deserialization attacks) are present in the classpath, the attacker can execute arbitrary system commands by crafting specific JDBC URLs (e.g., using H2's RUNSCRIPT command).

• Source: ⚠️ https://www.yuque.com/la12138/pa2fpb/sg81mhkrat5h170c?singleDoc
• User: Saul1213 (UID 94577)
• Submission: 02/21/2026 14:19 (1 month ago)
• Moderation: 03/01/2026 07:55 (8 days later)
• Status: Accepted
• VulDB entry: 348300 [thinkgem JeeSite up to 5.15.1 Connection path traversal]
• Points: 20