CVE-2026-0550 MEDIUM

CVE-2026-0550: myCred <= 2.9.7.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'mycred_load_coupon' Shortcode

Vendor Saadiqbal
Product Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program – myCred
Weakness CWE-79 · XSS
Published February 14, 2026
Last update April 8, 2026

CVSS base score

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

CVSS vector

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

What the vulnerability does

01Description

The myCred plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'mycred_load_coupon' shortcode in all versions up to, and including, 2.9.7.3 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Explanation of Vulnerability in Simple Terms

02Summary

myCred versions up to 2.9.7.3 contain a cross-site scripting vulnerability that allows authenticated users to inject malicious scripts affecting other users across the site. An attacker with low-level account access can craft input that executes in other users' browsers, potentially stealing session data or performing actions on their behalf. The vulnerability has a changed scope, meaning the impact extends beyond the vulnerable component itself.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that execute in other users' browsers and steal their session data or perform actions on their behalf.

Potential impact on your site

04Site Impact

Site users' accounts and data are at risk; attackers can hijack sessions or perform unauthorized actions as legitimate users.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege account on the site; no user interaction required from the victim.

Key dates

06Disclosure timeline

February 14, 2026 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE