CVE-2025-6738
BaseFortify
Publication date: 2025-06-27
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-6738 is a critical SQL injection vulnerability in the huija bicycleSharingServer application. It occurs in the function userDao.selectUserByUserNameLike within the UserServiceImpl.java file. The vulnerability arises because the username parameter is not properly sanitized, allowing an attacker to inject malicious SQL code remotely. This can lead to unauthorized execution of database commands, potentially compromising the system's confidentiality, integrity, and availability. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow an attacker to execute arbitrary SQL commands on the backend database by injecting malicious input through the username parameter. This can lead to unauthorized data access, data modification, or deletion, and potentially full compromise of the affected system. Since the vulnerable function is called with high-privilege user context (e.g., root), the impact can be severe, including loss of data confidentiality, integrity, and availability. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by sending crafted HTTP GET requests to the vulnerable endpoint and observing the response for SQL injection behavior. Specifically, you can test the endpoint `/bicycleSharingServer_war/admin-user-searchuser-show?username=` with payloads that include SQL injection patterns, such as appending special characters or SQL syntax to the username parameter. For example, using curl: `curl -v "http://localhost:8081/bicycleSharingServer_war/admin-user-searchuser-show?username=root*"`. Additionally, automated SQL injection detection tools like sqlmap can be used to confirm the vulnerability by targeting this endpoint and parameter. Example sqlmap command: `sqlmap -u "http://localhost:8081/bicycleSharingServer_war/admin-user-searchuser-show?username=root" --risk=3 --level=5`. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable endpoint to trusted users only, applying input validation and sanitization on the username parameter to prevent SQL injection, and monitoring for suspicious activity targeting the user search functionality. Since no patches or fixes are currently available, consider disabling or restricting the affected feature until a secure update or alternative solution is implemented. Replacing the affected component or applying a web application firewall (WAF) with SQL injection protection rules can also help reduce risk. [3, 2]