CVE-2025-15354
SQL Injection in itsourcecode SMS 1.0 /admin/add_admin.php
Publication date: 2025-12-30
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 | society_management_system | 1.0 |
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-15354 is a critical SQL injection vulnerability in the itsourcecode Society Management System version 1.0, specifically in the /admin/add_admin.php file. The vulnerability arises because the 'username' parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially manipulating the database by executing unauthorized queries. Various SQL injection techniques such as boolean-based blind, error-based, and time-based blind injections can be used to exploit this flaw. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive data, unauthorized modification or deletion of data, full system compromise, and disruption of services. Attackers can manipulate the database remotely without needing to authenticate, threatening system security and business continuity. [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 /admin/add_admin.php endpoint for SQL injection via the 'username' parameter. You can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://target/admin/add_admin.php" --data="username=admin" --risk=3 --level=5 --batch. Additionally, manual testing with payloads such as 'username=-2084' OR 3880=3880 #' (boolean-based blind), error-based payloads using MySQL functions, or time-based payloads like 'username=admin123' AND (SELECT SLEEP(5))--' can help identify the vulnerability. Attackers may also use Google dorking with the query inurl:admin/add_admin.php to find vulnerable targets. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection. 2) Enforce strict input validation and filtering on the 'username' parameter to ensure it conforms to expected formats. 3) Minimize database user privileges by avoiding use of high-privilege accounts for routine operations. 4) Conduct regular security audits to detect and address vulnerabilities promptly. If possible, replace the affected component with a secure alternative. These steps help secure the system and protect data integrity. [1, 2, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access, data leakage, and data tampering due to SQL injection, which can lead to exposure or modification of sensitive information. Such impacts can result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive data against unauthorized access and breaches. Therefore, this vulnerability poses a significant risk to compliance with these common standards and regulations. [1, 2, 3]