CVE-2024-43214

myCred <= 2.7.2 - Unauthenticated Information Exposure

2024-08-09 00:00
Kévin Mosbahi (Mika)

Strategic Overview

Status
Patched in 2.7.3
Affected Version
<= 2.7.2
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2024-43214
View all Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program – myCred vulnerabilities

At a glance

CVE-2024-43214 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program WordPress plugin, affecting versions <= 2.7.2. 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.3; sites on affected versions should update now. Disclosed August 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 Information Exposure in all versions up to, and including, 2.7.2 via the get_issuer_data() function. This makes it possible for unauthenticated attackers to see the open badge email.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program <= 2.7.2 carries this weakness at get_issuer_data(), and reaching it takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program the fix is 2.7.3: builds <= 2.7.2 are affected, anything from 2.7.3 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

Related records

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