CVE-2026-36947
SQL Injection in Sourcecodester Repair Shop Management System
Publication date: 2026-04-13
Last updated on: 2026-04-14
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| oretnom23 | 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?
CVE-2026-36947 is an SQL injection vulnerability found in the Computer and Mobile Repair Shop Management System v1.0 by Sourcecodester. The flaw exists in the file /rsms/admin/services/view_service.php, where the 'id' parameter in the URL query string is not properly sanitized. This allows an attacker to inject malicious SQL code through the 'id' parameter.
The vulnerability enables an attacker to execute arbitrary SQL commands on the backend database named 'rsms_db'. For example, an attacker can use a UNION-based SQL injection payload to retrieve sensitive information such as the current database name.
The root cause of this vulnerability is insufficient input validation and sanitization in the view_service.php script, which is developed using PHP 8.1 on the XAMPP platform.
How can this vulnerability impact me? :
This SQL injection vulnerability can have serious impacts including unauthorized disclosure of sensitive data stored in the rsms_db database.
An attacker could manipulate or extract data by executing arbitrary SQL commands, potentially leading to data breaches, data loss, or unauthorized modification of information within the system.
Such impacts could compromise the confidentiality, integrity, and availability of the system's data.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the `id` parameter in the URL query string of the file `/rsms/admin/services/view_service.php` for SQL injection flaws.
A common detection method is to send a crafted HTTP request with a malicious payload to see if the system is vulnerable.
For example, you can use curl or a similar tool to send a request like:
- curl "http://<target>/rsms/admin/services/view_service.php?id=-1' union select 1,database(),3,4,5,6,7--+"
If the response contains the database name or other unexpected data, it indicates the presence of the SQL injection vulnerability.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the Sourcecodester Computer and Mobile Repair Shop Management System v1.0 allows attackers to execute arbitrary SQL commands, potentially leading to unauthorized disclosure or manipulation of data stored in the system's database.
Such unauthorized access or data breaches can compromise the confidentiality and integrity of personal or sensitive information, which may result in non-compliance with data protection regulations and standards such as GDPR or HIPAA.
Organizations using this vulnerable system could face legal and regulatory consequences if personal data is exposed or altered due to exploitation of this flaw.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the SQL injection vulnerability in /rsms/admin/services/view_service.php, immediate steps include implementing proper input validation and sanitization on the 'id' parameter to prevent malicious SQL code execution.
Additionally, applying parameterized queries or prepared statements in the PHP code handling the database queries will help prevent injection attacks.
As a temporary measure, restricting access to the vulnerable script or disabling the affected functionality until a secure fix is deployed can reduce risk.