myCred – Loyalty Points and Rewards plugin for WordPress and WooCommerce – Give Points, Ranks, Badges, Cashback, WooCommerce rewards, and WooCommerce credits for Gamification <= 2.7.3 - Missing Authorization to Unauthenticated Database Upgrade
Strategic Overview
- Status
- Patched in 2.7.4
- Affected Plugin
- Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program – myCred
- Affected Version
<= 2.7.3- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-8658
At a glance
CVE-2024-8658 is a medium-severity Missing Authorization vulnerability in the Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program WordPress plugin, affecting versions <= 2.7.3. 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 2.7.4; sites on affected versions should update now. Disclosed September 2024, reported by Kévin Mosbahi (Mika).
Vulnerability Overview
The myCred – Loyalty Points and Rewards plugin for WordPress and WooCommerce – Give Points, Ranks, Badges, Cashback, WooCommerce rewards, and WooCommerce credits for Gamification plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the mycred_update_database() function in all versions up to, and including, 2.7.3. This makes it possible for unauthenticated attackers to upgrade an out of date database.
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
Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program <= 2.7.3 carries this weakness at mycred_update_database(), and reaching it takes no account at all. 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 Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program the fix is 2.7.4: builds <= 2.7.3 are affected, anything from 2.7.4 onward is not.
Remediation
Update to version 2.7.4, 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: Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program 2.7.4 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 Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program – myCred
- 8.8CVE-2021-24755: myCred Subscriber+ SQL Injection
CVE-2021-24755 - 8.1CVE-2024-43354: myCred <= 2.7.2 PHP Object Injection
CVE-2024-43354 - 6.4CVE-2026-17149: myCred Stored XSS
CVE-2026-17149 - 6.4CVE-2026-8607: myCred Stored XSS
CVE-2026-8607 - 6.4CVE-2026-42676: Points Management System… Stored XSS
CVE-2026-42676 - 6.4CVE-2026-0550: myCred <= 2.9.7.3 Stored Cross-Site Scripting
CVE-2026-0550 - 6.4CVE-2026-27440: myCred Stored XSS
CVE-2026-27440 - 6.4CVE-2025-54668: myCred <= 2.9.4.3 Stored Cross-Site Scripting
CVE-2025-54668
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C