CVE-2023-35096

myCred <= 2.5 - Cross-Site Request Forgery

2023-06-14 00:00
István Márton

Strategic Overview

Status
Patched in 2.5.1
Affected Plugin
Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program – myCred
Affected Version
< 2.5.1
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-35096
View all Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program – myCred vulnerabilities

At a glance

CVE-2023-35096 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program WordPress plugin, affecting versions < 2.5.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.5.1; sites on affected versions should update now. Disclosed June 2023, reported by István Márton.

Vulnerability Overview

The myCred plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.5. This is due to missing nonce validation on the mycred_save_license() function. This makes it possible for unauthenticated attackers to modify the plugin's membership key via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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.

CWE-352: Cross-Site Request Forgery (CSRF)

Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program < 2.5.1 carries this weakness at mycred_save_license(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program the fix is 2.5.1: builds < 2.5.1 are affected, anything from 2.5.1 onward is not.

Remediation

Update to version 2.5.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program 2.5.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-35096https://www.wordfence.com/threat-intel/vulnerabilities/id/a3936c4b-2326-41dc-b7d6-a8cf43752ddbhttps://nvd.nist.gov/vuln/detail/CVE-2023-35096

Related records

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