Frappe ERPNext v11.x.x-develop b1036e5 Comment cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Frappe ERPNext v11.x.x-develop b1036e5. It has been classified as problematic. Affected by this issue is some unknown functionality of the component Comment. Performing a manipulation results in cross site scripting. This vulnerability was named CVE-2018-11339. The attack may be initiated remotely. In addition, an exploit is available.
Details
A vulnerability classified as problematic has been found in Frappe ERPNext v11.x.x-develop b1036e5. This affects an unknown code block of the component Comment. The manipulation with an unknown input leads to a cross site scripting vulnerability. 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. The summary by CVE is:
An XSS issue was discovered in Frappe ERPNext v11.x.x-develop b1036e5 via a comment.
The bug was discovered 05/22/2018. The weakness was presented 05/22/2018 (Website). The advisory is shared at discuss.erpnext.com. This vulnerability is uniquely identified as CVE-2018-11339 since 05/21/2018. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (44691). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
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
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: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
Timeline
05/21/2018 🔍05/21/2018 🔍
05/22/2018 🔍
05/22/2018 🔍
05/22/2018 🔍
10/21/2024 🔍
Sources
Advisory: 5546Status: Not defined
CVE: CVE-2018-11339 (🔍)
GCVE (CVE): GCVE-0-2018-11339
GCVE (VulDB): GCVE-100-118053
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 05/22/2018 10:43Updated: 10/21/2024 21:54
Changes: 05/22/2018 10:43 (56), 02/07/2020 19:34 (4), 03/14/2023 14:45 (4), 10/21/2024 21:54 (16)
Complete: 🔍
Cache ID: 216::103
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.