CVE-2026-36945
SQL Injection in Sourcecodester Repair Shop Management System
Publication date: 2026-04-13
Last updated on: 2026-04-13
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| sourcecodester | computer_and_mobile_repair_shop_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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Computer and Mobile Repair Shop Management System v1.0 by Sourcecodester has an SQL injection vulnerability in the file /rsms/admin/clients/manage_client.php.
This vulnerability occurs at the URL parameter 'id' in requests to that PHP file, allowing an attacker to inject malicious SQL code.
For example, an attacker can use a UNION-based SQL injection payload to retrieve sensitive information such as the current database name.
This means unauthorized users can manipulate database queries to leak data from the system.
How can this vulnerability impact me? :
This SQL injection vulnerability can lead to unauthorized data leakage from the database.
Attackers exploiting this flaw can access sensitive information stored in the database, potentially compromising client data and system integrity.
Such unauthorized access can result in data breaches, loss of confidentiality, and damage to the organization's reputation.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by sending crafted HTTP requests to the vulnerable URL parameter and observing the response for SQL errors or unexpected data.
An example command to test this vulnerability using curl is:
- curl "http://<target>/rsms/admin/clients/manage_client.php?id=-2' union select 1, database(), 3, 4, 5, 6, 7, 8, 9, 10--+"
This command injects a UNION-based SQL payload into the 'id' parameter to check if the database name is returned, indicating a successful SQL injection.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability is an SQL injection that allows unauthorized data leakage from the database. Such unauthorized access to sensitive data can lead to non-compliance with data protection regulations like GDPR and HIPAA, which require the protection of personal and sensitive information.
Specifically, if personal or health-related data is stored in the affected system, this vulnerability could result in exposure of that data, violating confidentiality and data protection requirements mandated by these standards.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the SQL injection vulnerability in /rsms/admin/clients/manage_client.php, immediate steps include:
- Validate and sanitize all user inputs, especially the 'id' parameter, to prevent malicious SQL code injection.
- Use prepared statements or parameterized queries in the PHP code to safely handle database queries.
- Restrict database user permissions to limit the impact of any potential injection.
- Monitor and review logs for suspicious activity related to the vulnerable endpoint.
- Apply patches or updates from the vendor if available.