CVE-2025-15196
SQL Injection in Assessment Management 1.0 login.php Allows Remote Exploit
Publication date: 2025-12-29
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 |
|---|---|---|
| code-projects | assessment_management | 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
How can this vulnerability impact me? :
The vulnerability can allow a remote attacker to perform SQL injection attacks, which may lead to unauthorized access, data leakage, data modification, or disruption of the application. This can compromise the confidentiality, integrity, and availability of the system and its data.
Can you explain this vulnerability to me?
This vulnerability exists in code-projects Assessment Management 1.0 within the login.php file. It involves manipulation of the userid argument, which leads to a SQL injection vulnerability. This means an attacker can remotely inject malicious SQL code through the userid parameter to potentially access or manipulate the database.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'userid' parameter in the login.php file for SQL injection. One approach is to use tools like sqlmap to send crafted POST requests to /assessment/login.php with manipulated 'userid' values to check for SQL injection. For example, using sqlmap with a command targeting the URL and POST data 'userid=admin&password=Pass&submit=' can help enumerate databases if vulnerable. Additionally, attackers may use Google Dorking with queries like 'inurl:login.php' to identify vulnerable targets. Monitoring for unusual SQL errors or unexpected database responses in logs related to login.php may also help detect exploitation attempts. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding in the login.php code to separate SQL code from user input, preventing SQL injection. 2) Implement strict input validation and filtering on the 'userid' parameter to ensure it conforms to expected formats and blocks malicious input. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts like 'root' or 'admin' for routine operations. 4) Consider replacing the affected software with an alternative product if remediation is not feasible. These actions are critical to protect system security and maintain data integrity. [1, 2, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized database access, sensitive data leakage, and data tampering, which can lead to violations of data protection regulations such as GDPR and HIPAA. Exploitation of this SQL injection flaw compromises confidentiality, integrity, and availability of data, potentially resulting in non-compliance with these standards that require protection of personal and sensitive information. [1, 2]