CVE-2025-7934

6.3 MEDIUM

📋 TL;DR

This CVE describes a critical SQL injection vulnerability in the fuyang_lipengjun platform's ScheduleJobController. Attackers can exploit this by manipulating the beanName parameter in the queryPage function to execute arbitrary SQL commands remotely. All deployments using versions up to commit ca9aceff6902feb7b0b6bf510842aea88430796a are affected.

💻 Affected Systems

Products:
  • fuyang_lipengjun platform
Versions: All versions up to commit ca9aceff6902feb7b0b6bf510842aea88430796a
Operating Systems: All platforms running Java
Default Config Vulnerable: ⚠️ Yes
Notes: The product does not use versioning, making precise version identification difficult. All deployments using the vulnerable code commit are affected.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data manipulation, and potential remote code execution through database functions.

🟠

Likely Case

Data exfiltration, privilege escalation, and unauthorized access to sensitive information stored in the database.

🟢

If Mitigated

Limited impact if proper input validation and parameterized queries are implemented, though some risk remains.

🌐 Internet-Facing: HIGH - The vulnerability can be exploited remotely without authentication, making internet-facing instances particularly vulnerable.
🏢 Internal Only: MEDIUM - Internal systems are still at risk from insider threats or compromised internal accounts.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploit details have been publicly disclosed and the vulnerability requires minimal technical skill to exploit.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown - product does not use versioning

Vendor Advisory: https://gitee.com/fuyang_lipengjun/platform/issues/ICLILS

Restart Required: Yes

Instructions:

1. Check the Gitee issue for any available fixes. 2. Apply manual code fixes to implement parameterized queries. 3. Rebuild and redeploy the application. 4. Restart the service.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement strict input validation for the beanName parameter to reject SQL injection attempts

Implement regex validation: ^[a-zA-Z0-9_]+$ for beanName parameter

WAF Rule

all

Deploy Web Application Firewall rules to block SQL injection patterns

Configure WAF to block requests containing SQL keywords in beanName parameter

🧯 If You Can't Patch

  • Isolate the vulnerable system behind a reverse proxy with strict input filtering
  • Implement network segmentation to limit database access from the application server

🔍 How to Verify

Check if Vulnerable:

Check if your deployment uses code from commit ca9aceff6902feb7b0b6bf510842aea88430796a or earlier in the ScheduleJobController.java file

Check Version:

git log --oneline -1 platform-schedule/src/main/java/com/platform/controller/ScheduleJobController.java

Verify Fix Applied:

Test the queryPage endpoint with SQL injection payloads in the beanName parameter to ensure they are rejected

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts from single IP
  • Requests with SQL keywords in beanName parameter

Network Indicators:

  • Unusual database connection patterns
  • Large data transfers from database server

SIEM Query:

source="application.logs" AND (beanName CONTAINS "UNION" OR beanName CONTAINS "SELECT" OR beanName CONTAINS "INSERT")

🔗 References

📤 Share & Export