WP Like Button <= 1.7.0 - Missing Authorization via crublabFBLBAjax
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- WP Like Button
- Affected Version
<= 1.7.0- CVSS
- 3.1Low
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2023-47820
At a glance
CVE-2023-47820 is a low-severity Missing Authorization vulnerability in the WP Like Button WordPress plugin, affecting versions <= 1.7.0. It carries a CVSS score of 3.1 (reachable over the network). The root cause is a missing authorization check on a reachable function. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed November 2023, reported by Abdi Pranata.
Vulnerability Overview
The WP Like Button plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the crublabFBLBAjax function in versions up to, and including, 1.7.0. This makes it possible for authenticated attackers, with subscriber-level access and above, to enable and disable the like button if they are able to retrieve a nonce via a nonce leak.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in WP Like Button <= 1.7.0 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. No fixed build of this plugin is recorded for WP Like Button yet, so installs running <= 1.7.0 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WP Like Button
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C