Yoast SEO Plugin up to 5.7.x on WordPress class-gsc-table.php cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Yoast SEO Plugin up to 5.7.x on WordPress. Affected is an unknown function of the file admin/google_search_console/class-gsc-table.php. The manipulation results in cross site scripting. This vulnerability is reported as CVE-2017-16842. The attack can be launched remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability was found in Yoast SEO Plugin up to 5.7.x on WordPress (WordPress Plugin). It has been classified as problematic. Affected is some unknown functionality of the file admin/google_search_console/class-gsc-table.php. 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. CVE summarizes:
Cross-site scripting (XSS) vulnerability in admin/google_search_console/class-gsc-table.php in the Yoast SEO plugin before 5.8.0 for WordPress allows remote attackers to inject arbitrary web script or HTML.
The bug was discovered 11/15/2017. The weakness was disclosed 11/16/2017 (Website). The advisory is available at packetstormsecurity.com. This vulnerability is traded as CVE-2017-16842 since 11/15/2017. It is possible to launch the attack remotely. A authentication is required for exploitation. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1059.007 by the MITRE ATT&CK project.
By approaching the search of inurl:admin/google_search_console/class-gsc-table.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 5.8.0 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.6VulDB Meta Temp Score: 3.5
VulDB Base Score: 2.4
VulDB Temp Score: 2.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.8
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 |
OpenVAS ID: 881279
OpenVAS Name: WordPress Yoast SEO Plugin XSS Vulnerability
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Yoast SEO Plugin 5.8.0
Timeline
11/15/2017 🔍11/15/2017 🔍
11/15/2017 🔍
11/16/2017 🔍
11/16/2017 🔍
01/24/2021 🔍
Sources
Advisory: 1766831Status: Not defined
CVE: CVE-2017-16842 (🔍)
GCVE (CVE): GCVE-0-2017-16842
GCVE (VulDB): GCVE-100-109482
Entry
Created: 11/16/2017 17:47Updated: 01/24/2021 08:32
Changes: 11/16/2017 17:47 (62), 12/07/2019 09:21 (1), 01/24/2021 08:32 (2)
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.