Rate My Post – Star Rating Plugin by FeedbackWP <= 4.2.4 - Unauthenticated Voting On Scheduled Posts
Strategic Overview
- Status
- Patched in 4.2.5
- Affected Plugin
- Rate My Post – Star Rating Plugin by FeedbackWP
- Affected Version
<= 4.2.4- CVSS
- 5.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2024-12309
At a glance
CVE-2024-12309 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Rate My Post WordPress plugin, affecting versions <= 4.2.4. 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 4.2.5; sites on affected versions should update now. Disclosed December 2024, reported by HayMiz.
Vulnerability Overview
The Rate My Post – Star Rating Plugin by FeedbackWP plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.2.4 via the get_post_status() due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to vote on unpublished scheduled posts.
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-639: Authorization Bypass Through User-Controlled Key
Rate My Post <= 4.2.4 carries this weakness at get_post_status(), and reaching it takes no account at all. 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 Rate My Post the fix is 4.2.5: builds <= 4.2.4 are affected, anything from 4.2.5 onward is not.
Remediation
Update to version 4.2.5, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Rate My Post 4.2.5 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Rate My Post – Star Rating Plugin by FeedbackWP
- 8.8CVE-2022-40671: Rate my Post – WP Rating System <= 3.3.4 CSRF
CVE-2022-40671 - 6.4CVE-2022-4673: Rate my Post – WP Rating System <= 3.3.8 Stored XSS
CVE-2022-4673 - 5.3CVE-2023-51667: Rate my Post – WP Rating System IP Address Spoofing
CVE-2023-51667 - 4.3CVE-2022-40310: Rate my Post – WP Rating System Race Condition
CVE-2022-40310
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C