Go Pricing - WordPress Responsive Pricing Tables <= 3.3.19 - Missing Authorization to Limited Privilege Granting
Strategic Overview
- Status
- Patched in 3.4
- Affected Plugin
- Go Pricing - WordPress Responsive Pricing Tables
- Affected Version
<= 3.3.19- CVSS
- 4.6Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2023-2494
At a glance
CVE-2023-2494 is a medium-severity Missing Authorization vulnerability in the Go Pricing - WordPress Responsive Pricing Tables WordPress plugin, affecting versions <= 3.3.19. It carries a CVSS score of 4.6 (reachable over the network). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 3.4; sites on affected versions should update now. Disclosed May 2023, reported by István Márton.
Vulnerability Overview
The Go Pricing - WordPress Responsive Pricing Tables plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'process_postdata' function in versions up to, and including, 3.3.19. This makes it possible for authenticated attackers with a role that the administrator previously granted access to the plugin to modify access to the plugin when it should only be the administrator's privilege.
Technical Analysis
The vector marks this flaw as remotely reachable over the network.
CWE-862: Missing Authorization
Go Pricing - WordPress Responsive Pricing Tables <= 3.3.19 carries this weakness at process_postdata, and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Go Pricing - WordPress Responsive Pricing Tables the fix is 3.4: builds <= 3.3.19 are affected, anything from 3.4 onward is not.
Remediation
Update to version 3.4, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Go Pricing - WordPress Responsive Pricing Tables 3.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Go Pricing - WordPress Responsive Pricing Tables
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C