CVE-2025-15353
SQL Injection in itsourcecode SMS 1.0 edit_admin_query (Remote
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-15353 is a critical SQL injection vulnerability in the Society Management System version 1.0, specifically in the function edit_admin_query within the file /admin/edit_admin_query.php. The vulnerability occurs because the application does not properly validate or sanitize the 'username' parameter, allowing attackers to inject malicious SQL code remotely without authentication. This can lead to unauthorized database access, data leakage, modification, deletion, or even full system compromise. Various SQL injection techniques such as Boolean-based blind, error-based, and time-based blind SQL injection have been demonstrated to exploit this flaw. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can allow attackers to gain unauthorized access to the database, leading to exposure of sensitive information, unauthorized modification or deletion of data, and potential disruption of system services. Because no authentication is required to exploit it, attackers can remotely compromise the system, potentially resulting in full system compromise or service disruption. [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 'username' parameter in the /admin/edit_admin_query.php file for SQL injection. You can use SQL injection payloads such as Boolean-based blind SQL injection (e.g., username=-2084' OR 3880=3880 #), error-based SQL injection, or time-based blind SQL injection (e.g., username=admin123' AND (SELECT SLEEP(5))--). Tools like sqlmap can automate detection by targeting the vulnerable parameter. Additionally, attackers may be identified by scanning for the URL pattern 'inurl:admin/edit_admin_query.php' using Google dorking to find vulnerable instances. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Implement strict input validation and filtering on the 'username' parameter to ensure it conforms to expected formats. 3) Minimize database user permissions by avoiding use of high-privilege accounts like 'root' or 'admin' for routine operations. 4) Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, consider replacing the affected product or applying vendor patches when available. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, since the vulnerability allows unauthorized database access, data leakage, modification, and deletion, it could potentially lead to violations of data protection requirements under such regulations if sensitive personal or health data is compromised. No direct statements about compliance impact are available. [1, 2, 3]