| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Formspree. Impacted is an unknown function of the file templates/forms/thanks.html. This manipulation of the argument _next as part of Parameter causes cross site scripting. This vulnerability appears as CVE-2018-6354. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability has been found in Formspree (affected version not known) and classified as problematic. Affected by this vulnerability is some unknown functionality of the file templates/forms/thanks.html. The manipulation of the argument _next as part of a Parameter leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect integrity. The summary by CVE is:
templates/forms/thanks.html in Formspree before 2018-01-23 allows XSS related to the _next parameter.
The bug was discovered 01/24/2018. The weakness was presented 01/27/2018 (Website). The advisory is shared at github.com. This vulnerability is known as CVE-2018-6354 since 01/27/2018. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
By approaching the search of inurl:templates/forms/thanks.html it is possible to find vulnerable targets with Google Hacking.
Upgrading eliminates this vulnerability. A possible mitigation has been published before and not just after the disclosure of the vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
License
Website
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: 🔍
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
01/23/2018 🔍01/24/2018 🔍
01/27/2018 🔍
01/27/2018 🔍
01/27/2018 🔍
01/28/2018 🔍
02/02/2023 🔍
Sources
Product: github.comAdvisory: 5f18eeaaa459bee9a58f70cdf7c46adb1ef34ea7
Status: Not defined
CVE: CVE-2018-6354 (🔍)
GCVE (CVE): GCVE-0-2018-6354
GCVE (VulDB): GCVE-100-112513
Entry
Created: 01/28/2018 09:38Updated: 02/02/2023 19:42
Changes: 01/28/2018 09:38 (57), 12/30/2019 09:48 (1), 02/02/2023 19:42 (5)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.