Supsystic Popup Plugin 1.7.6 on WordPress cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Supsystic Popup Plugin 1.7.6 on WordPress. This affects an unknown part. The manipulation leads to cross-site request forgery. This vulnerability is referenced as CVE-2017-20065. Remote exploitation of the attack is possible. Furthermore, an exploit is available.
Details
A vulnerability was found in Supsystic Popup Plugin 1.7.6 on WordPress (WordPress Plugin) and classified as problematic. This issue affects an unknown functionality. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. Impacted is integrity.
The weakness was published 03/01/2017 by Radjnies Bhansingh as Popup by Supsystic WordPress plugin vulnerable to Cross-Site Request Forgery as not defined mailinglist post (Full-Disclosure). The advisory is shared at seclists.org. The public release happened without involvement of Supsystic. The identification of this vulnerability is CVE-2017-20065. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are unknown but a public exploit is available.
A public exploit has been developed by Radjnies Bhansingh and been published immediately after the advisory. The exploit is available at exploit-db.com. It is declared as proof-of-concept.
The vendor claims: "[...] we have already released the fixes for these issues for a long time ago [...]"
The vulnerability is also documented in the vulnerability database at Exploit-DB (41485). map.httpcs.com is providing further details. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
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 request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Radjnies Bhansingh
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: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
03/01/2017 🔍03/01/2017 🔍
03/01/2017 🔍
03/01/2017 🔍
06/18/2022 🔍
Sources
Advisory: Popup by Supsystic WordPress plugin vulnerable to Cross-Site Request ForgeryResearcher: Radjnies Bhansingh
Status: Not defined
CVE: CVE-2017-20065 (🔍)
GCVE (CVE): GCVE-0-2017-20065
GCVE (VulDB): GCVE-100-97385
scip Labs: https://www.scip.ch/en/?labs.20161013
Misc.: 🔍
Entry
Created: 03/01/2017 17:40Updated: 06/18/2022 17:29
Changes: 03/01/2017 17:40 (47), 11/25/2019 15:47 (3), 06/18/2022 17:29 (6)
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.