CVE-2025-12362

myCred – Points Management System For Gamification, Ranks, Badges, and Loyalty Program <= 2.9.7 - Missing Authorization to Unauthenticated Withdrawal Request Approval

2025-12-12 17:05
Rafshanzani Suhada

Strategic Overview

Status
Patched in 2.9.7.1
Affected Plugin
Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program – myCred
Affected Version
<= 2.9.7
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-12362
View all Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program – myCred vulnerabilities

At a glance

CVE-2025-12362 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.9.7. 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.9.7.1; sites on affected versions should update now. Disclosed December 2025, reported by Rafshanzani Suhada.

Vulnerability Overview

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. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to approve withdrawal requests, modify user point balances, and manipulate the payment processing system via the cashcred_pay_now AJAX action.

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

Reaching this weakness in Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program <= 2.9.7 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.9.7.1: builds <= 2.9.7 are affected, anything from 2.9.7.1 onward is not.

Remediation

Update to version 2.9.7.1, 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.9.7.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-12362https://www.wordfence.com/threat-intel/vulnerabilities/id/af54654b-60af-446d-b170-ee0a1ebed22chttps://nvd.nist.gov/vuln/detail/CVE-2025-12362

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C