CVE-2025-10405
BaseFortify
Publication date: 2025-09-14
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 |
|---|---|---|
| itsourcecode | baptism_information_management_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-10405 is a critical SQL injection vulnerability in the itsourcecode Baptism Information Management System version 1.0, specifically in the /listbaptism.php file. The vulnerability arises because the 'bapt_id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This flaw enables attackers to manipulate database queries remotely without authentication, potentially compromising the confidentiality, integrity, and availability of the system. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data manipulation, and full system control. Attackers can retrieve, modify, or delete sensitive information, disrupt services, and compromise business continuity. Since no authentication is required, the attack can be executed remotely and easily, posing a severe threat to system security. [1, 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 /listbaptism.php endpoint for SQL injection on the 'bapt_id' parameter. One approach is to use automated tools like sqlmap with a command such as: sqlmap -u "http://target/listbaptism.php" --data="bapt_id=1&lname=test&submit=" --risk=3 --level=5. Additionally, Google Dorking can help identify vulnerable targets using the query: inurl:listbaptism.php. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replace the affected software with an alternative product if possible. 2) Apply prepared statements with parameter binding to prevent SQL injection. 3) Implement strict input validation and filtering on the 'bapt_id' parameter. 4) Minimize database user permissions by avoiding use of high-privilege accounts for routine operations. 5) Conduct regular security audits to detect and address vulnerabilities promptly. [1, 2]