Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2022-2171 | First vendor Publication | 2022-08-01 |
Vendor | Cve | Last vendor Modification | 2024-11-21 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N | |||
---|---|---|---|
Overall CVSS Score | 5.4 | ||
Base Score | 5.4 | Environmental Score | 5.4 |
impact SubScore | 2.7 | Temporal Score | 5.4 |
Exploitabality Sub Score | 2.3 | ||
Attack Vector | Network | Attack Complexity | Low |
Privileges Required | Low | User Interaction | Required |
Scope | Changed | Confidentiality Impact | Low |
Integrity Impact | Low | Availability Impact | None |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : | |||
---|---|---|---|
Cvss Base Score | N/A | Attack Range | N/A |
Cvss Impact Score | N/A | Attack Complexity | N/A |
Cvss Expoit Score | N/A | Authentication | N/A |
Calculate full CVSS 2.0 Vectors scores |
Detail
The Progressive License WordPress plugin through 1.1.0 is lacking any CSRF check when saving its settings, which could allow attackers to make a logged in admin change them. Furthermore, as the plugin allows arbitrary HTML to be inserted in one of the settings, this could lead to Stored XSS issue which will be triggered in the frontend as well. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2171 |
Sources (Detail)
Source | Url |
---|
Alert History
Date | Informations |
---|---|
2024-11-28 14:06:16 |
|
2022-08-06 00:27:13 |
|
2022-08-01 17:27:10 |
|