Tabs – Responsive Tabs with WooCommerce Product Tab Extension <= 3.6.0 - Authenticated (Admin+) Arbitrary Options Update
Strategic Overview
- Status
- Patched in 3.7.0
- Affected Version
<= 3.6.0- CVSS
- 7.2High
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2022-36375
At a glance
CVE-2022-36375 is a high-severity Authorization Bypass Through User-Controlled Key vulnerability in the Tabs WordPress plugin, affecting versions <= 3.6.0. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 3.7.0; sites on affected versions should update now. Disclosed July 2022, reported by R3N0.
Vulnerability Overview
The Tabs – Responsive Tabs with WooCommerce Product Tab Extension plugin for WordPress is vulnerable to arbitrary options updates in versions up to, and including, 3.6.8. This is due to a lack of validation on the settings supplied to the post_oxi_settings() function. This makes it possible for authenticated attackers, with administrative level permissions, to update arbitrary options on the WordPress site. This would only affect sites where the administrator has been restricted to not 'manage_options' or the administrator has allowed users with lower permissions to update the plugin's settings.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-639: Authorization Bypass Through User-Controlled Key
Tabs <= 3.6.0 carries this weakness at manage_options, and reaching it takes an account at Admin level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Tabs the fix is 3.7.0: builds <= 3.6.0 are affected, anything from 3.7.0 onward is not.
Remediation
Update to version 3.7.0, 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: Tabs 3.7.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Tabs – Responsive Tabs with WooCommerce Product Tab Extension
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C