Optimize Database after Deleting Revisions <= 5.0.110 - Missing Authorization via 'odb_csv_download'
Strategic Overview
- Status
- Patched in 5.1
- Affected Plugin
- Optimize Database after Deleting Revisions
- Affected Version
<= 5.0.110- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE pending
At a glance
This record tracks a medium-severity Missing Authorization vulnerability in the Optimize Database after Deleting Revisions WordPress plugin, affecting versions <= 5.0.110. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.1; sites on affected versions should update now. Disclosed October 2023.
Vulnerability Overview
The Optimize Database after Deleting Revisions plugin for WordPress is vulnerable to information disclosure in versions up to, and including, 5.0.110. This is due to a missing capability check on the 'odb_csv_download' function which is hooked via admin_init. This makes it possible for unauthenticated attackers to trigger a download of the plugin's data.
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 privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Optimize Database after Deleting Revisions <= 5.0.110 carries this weakness at odb_csv_download, 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 Optimize Database after Deleting Revisions the fix is 5.1: builds <= 5.0.110 are affected, anything from 5.1 onward is not.
Remediation
Update to version 5.1, 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: Optimize Database after Deleting Revisions 5.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Optimize Database after Deleting Revisions
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C