code-projects Client Details System 1.0 /admin/regester.php fname/lname/email/contact cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in code-projects Client Details System 1.0. The impacted element is an unknown function of the file /admin/regester.php. Such manipulation of the argument fname/lname/email/contact leads to cross site scripting. This vulnerability is documented as CVE-2023-7143. The attack can be executed remotely. Additionally, an exploit exists.
Details
A vulnerability was found in code-projects Client Details System 1.0 (Project Management Software). It has been rated as problematic. Affected by this issue is some unknown functionality of the file /admin/regester.php. The manipulation of the argument fname/lname/email/contact 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 weakness was released 12/28/2023. The advisory is available at github.com. This vulnerability is handled as CVE-2023-7143. Successful exploitation requires user interaction by the victim. Technical details as well as a public exploit are known. This vulnerability is assigned to T1059.007 by the MITRE ATT&CK project.
The exploit is available at github.com. It is declared as proof-of-concept. By approaching the search of inurl:admin/regester.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 best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://code-projects.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.2VulDB Meta Temp Score: 3.1
VulDB Base Score: 2.4
VulDB Temp Score: 2.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.8
NVD Vector: 🔍
CNA Base Score: 2.4
CNA Vector (VulDB): 🔍
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: 🔍
NVD Base Score: 🔍
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: 🔍
Timeline
12/28/2023 🔍12/28/2023 🔍
12/28/2023 🔍
10/29/2025 🔍
Sources
Vendor: code-projects.orgAdvisory: github.com
Status: Not defined
CVE: CVE-2023-7143 (🔍)
GCVE (CVE): GCVE-0-2023-7143
GCVE (VulDB): GCVE-100-249146
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 12/28/2023 09:28Updated: 10/29/2025 20:07
Changes: 12/28/2023 09:28 (42), 01/20/2024 09:20 (2), 01/20/2024 09:21 (28), 10/29/2025 20:07 (23)
Complete: 🔍
Submitter: Hamdi Sevben
Cache ID: 216::103
Submit
Accepted
- Submit #258501: code-projects Client Details System 1.0 Blind Cross Site Scripting (by Hamdi Sevben)
Duplicate
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.