CVE-2025-12361 MEDIUM

CVE-2025-12361: myCred – Points Management System For Gamification, Ranks, Badges, and Loyalty Program <= 2.9.7.1 - Missing Authorization to Sensitive Information Exposure

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

CVSS base score

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

CVSS vector

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

What the vulnerability does

01Description

The myCred – Points Management System For Gamification, Ranks, Badges, and Loyalty Program plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 2.9.7.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve sensitive information including user IDs, display names, and email addresses of all users on the site via the get_bank_accounts AJAX action. Passwords are not exposed.

Explanation of Vulnerability in Simple Terms

02Summary

myCred, a WordPress gamification plugin, fails to properly check user permissions before allowing access to certain functions. A logged-in user with low privileges can read sensitive data they shouldn't have access to. The vulnerability affects all versions up to 2.9.7.1. A patch version has not been publicly identified.

What an attacker can do

03Attacker Capabilities

Read sensitive data belonging to other users or the site without proper authorization.

Potential impact on your site

04Site Impact

User data and site information may be exposed to low-privilege account holders who should not have access.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege account on the site (e.g., subscriber or contributor role).

Key dates

06Disclosure timeline

December 19, 2025 CVE published
April 8, 2026 Record updated