CVE-2024-8658 MEDIUM

CVE-2024-8658: 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

Vendor Saadiqbal
Product Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program – myCred
Weakness CWE-862 · Missing authorization
Published September 25, 2024
Last update April 8, 2026

CVSS base score

5.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

The myCred Points Management System plugin for WordPress contains a missing authorization check that allows unauthenticated attackers to modify data on the site. An attacker can send a network request to alter points, badges, or other gamification elements without needing to log in or interact with a user. This affects all versions up to 2.7.3.

What an attacker can do

03Attacker Capabilities

Modify points, badges, ranks, or loyalty rewards data without authentication.

Potential impact on your site

04Site Impact

Attackers can tamper with gamification data, corrupting user rewards and site integrity without your knowledge.

Conditions required to exploit

05Prerequisites

Network access to the WordPress site; no authentication or user interaction required.

Key dates

06Disclosure timeline

September 25, 2024 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE