SourceCodester Hospital Patient Records Management System 1.0 doctors.php specialization cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in SourceCodester Hospital Patient Records Management System 1.0. Impacted is an unknown function of the file doctors.php. The manipulation of the argument specialization leads to cross site scripting. This vulnerability is traded as CVE-2022-22851. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.
Details
A vulnerability was found in SourceCodester Hospital Patient Records Management System 1.0 (Medical Device Software) and classified as problematic. This issue affects some unknown functionality of the file doctors.php. The manipulation of the argument specialization with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:
A Stored Cross Site Scripting (XSS) vulnerability exists in Sourcecodtester Hospital's Patient Records Management System 1.0 via the specialization parameter in doctors.php
The weakness was shared 01/26/2022 as 17381378bdb7c9f7b3326af6fb79cf68ca9f9d3d. The advisory is shared at github.com. The identification of this vulnerability is CVE-2022-22851 since 01/10/2022. It demands that the victim is doing some kind of user interaction. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
The exploit is available at github.com. It is declared as proof-of-concept. By approaching the search of inurl:doctors.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.sourcecodester.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.5
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
01/10/2022 🔍01/26/2022 🔍
01/26/2022 🔍
05/26/2026 🔍
Sources
Vendor: sourcecodester.comAdvisory: 17381378bdb7c9f7b3326af6fb79cf68ca9f9d3d
Status: Confirmed
CVE: CVE-2022-22851 (🔍)
GCVE (CVE): GCVE-0-2022-22851
GCVE (VulDB): GCVE-100-191669
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 01/26/2022 21:09Updated: 05/26/2026 08:04
Changes: 01/26/2022 21:09 (43), 01/29/2022 08:50 (2), 01/29/2022 08:53 (1), 05/26/2026 08:04 (20)
Complete: 🔍
Cache ID: 216::103
Submit
Duplicate
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.