CVE-2025-12243
BaseFortify
Publication date: 2025-10-27
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| fabian | client_details_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-12243 is a critical SQL Injection vulnerability in the code-projects Client Details System version 1.0. It occurs in the file clientdetails/welcome.php via the GET parameter 'ID'. The application directly inserts the 'ID' parameter into SQL queries without sanitization or use of prepared statements, allowing attackers to manipulate the SQL logic and inject arbitrary SQL code. This can be exploited remotely and enables various SQL injection techniques such as boolean-based, error-based, UNION-based, stacked queries, and time-based blind injections. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized data disclosure by allowing attackers to enumerate database metadata, extract tables, and dump records. It can also enable unauthorized data modification, including altering, corrupting, or deleting data if stacked queries or update paths are accessible. Attackers may bypass authentication and authorization controls if welcome.php manages session-related content. Additionally, with excessive database privileges, attackers can escalate to system compromise by reading local files or writing files accessible by the web server, potentially leading to remote code execution or full server takeover. Denial of service attacks are also possible by using time-based payloads to degrade service availability. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'ID' GET parameter in the file clientdetails/welcome.php for SQL injection. One can use tools like sqlmap to automate detection, for example: sqlmap -u "http://target/clientdetails/welcome.php?ID=1" --risk=3 --level=5. Additionally, manual testing can be done by injecting SQL payloads such as: ID=1' AND (SELECT 9698 FROM (SELECT(SLEEP(5)))rSxe)-- HUeU to observe time delays indicating a time-based blind SQL injection. Searching for the vulnerable URL pattern using Google dorking like "inurl:clientdetails/welcome.php" can help identify targets on the network. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing parameterized queries (prepared statements) to prevent SQL injection by separating SQL code from user input. Additionally, enforce the Principle of Least Privilege by restricting database user permissions to only necessary operations (e.g., SELECT, INSERT, UPDATE) and denying administrative privileges such as DROP, ALTER, or FILE access. If possible, replace the affected software with an alternative product. These measures help prevent exploitation and limit damage if an injection occurs. [2, 3]