WordPress security by component
Go Pricing - WordPress Responsive Pricing Tables
Plugin description
Go Pricing - WordPress Responsive Pricing Tables is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published May 25, 2023; the highest CVE/CNA score is 8.8.
Plugin slug:
go-pricingLatest vulnerability
CVE-2023-2500: Go Pricing - WordPress Responsive Pricing Tables: Code execution
Go Pricing - WordPress Responsive Pricing Tables is affected by code execution. Exploitation requires an authenticated WordPress account. Successful exploitation can run attacker-controlled code in the WordPress hosting account.
| Safe version |
|
||
|---|---|---|---|
| May 25, 2023 |
CVE-2023-2500
Go Pricing - WordPress Responsive Pricing Tables: Code execution
Go Pricing - WordPress Responsive Pricing Tables is affected by code execution. Exploitation requires an authenticated WordPress account. Successful exploitation can run attacker-controlled code in the WordPress hosting account.
|
See mitigation notes |
CVE8.8
NVD8.8
|
| May 24, 2023 |
CVE-2023-2498
Go Pricing - WordPress Responsive Pricing Tables: Cross-site scripting
Go Pricing - WordPress Responsive Pricing Tables is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.4
NVD5.4
|
| May 24, 2023 |
CVE-2023-2496
Go Pricing - WordPress Responsive Pricing Tables: Dangerous file upload
Go Pricing - WordPress Responsive Pricing Tables is affected by dangerous file upload. Exploitation requires an authenticated WordPress account. Successful exploitation can place attacker-controlled executable content on the server and may lead to full site compromise.
|
See mitigation notes |
CVE7.1
NVD7.5
|
| May 24, 2023 |
CVE-2023-2494
Go Pricing - WordPress Responsive Pricing Tables: A security weakness
Go Pricing - WordPress Responsive Pricing Tables is affected by a security weakness. Exploitation requires an authenticated WordPress account. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE4.6
NVD8.8
|