Dolibarr 8.0.2 public/notice.php transphrase Reflected cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in Dolibarr 8.0.2. This issue affects some unknown processing of the file public/notice.php. The manipulation of the argument transphrase as part of Parameter results in cross site scripting (Reflected). This vulnerability is reported as CVE-2018-19993. The attack can be launched remotely. No exploit exists.
Details
A vulnerability classified as problematic has been found in Dolibarr 8.0.2 (Enterprise Resource Planning Software). Affected is an unknown functionality of the file public/notice.php. The manipulation of the argument transphrase as part of a Parameter leads to a cross site scripting vulnerability (Reflected). CWE is classifying the issue as 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. This is going to have an impact on integrity. CVE summarizes:
A reflected cross-site scripting (XSS) vulnerability in Dolibarr 8.0.2 allows remote attackers to inject arbitrary web script or HTML via the transphrase parameter to public/notice.php.
The bug was discovered 12/20/2018. The weakness was disclosed 01/03/2019 (Website). The advisory is available at github.com. This vulnerability is traded as CVE-2018-19993 since 12/09/2018. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1059.007 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 14 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:public/notice.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.
The entries VDB-128685, VDB-128684, VDB-128683 and VDB-128681 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.7
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD Vector: 🔍
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
Name: ReflectedClass: Cross site scripting / Reflected
CWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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
12/09/2018 🔍12/20/2018 🔍
01/03/2019 🔍
01/03/2019 🔍
01/04/2019 🔍
06/23/2023 🔍
Sources
Product: github.comAdvisory: fc3fcc5455d9a610b85723e89e8be43a41ad1378
Status: Not defined
CVE: CVE-2018-19993 (🔍)
GCVE (CVE): GCVE-0-2018-19993
GCVE (VulDB): GCVE-100-128682
See also: 🔍
Entry
Created: 01/04/2019 12:30Updated: 06/23/2023 07:57
Changes: 01/04/2019 12:30 (63), 04/26/2020 09:22 (1), 06/23/2023 07:57 (4)
Complete: 🔍
Cache ID: 216::103
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.