CVE-2026-123471: myCred stored XSS via content injection

CVE-2026-123471 · Severity: medium · CVSS 4.3 · Published 2026-11-06

myCred is a WordPress plugin that manages gamification and user engagement features on websites. A stored cross-site scripting (XSS) vulnerability allows attackers with subscriber-level access to inject malicious scripts into pages, which can be used to deface content, redirect visitors to malicious sites, or steal sensitive information from site visitors.

Technologies: myCred. Vendors: myCred.

Quick answers

Is CVE-2026-123471 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-123471 being exploited in the wild.
How severe is CVE-2026-123471?
Medium severity, with a CVSS score of 4.3, published 6 November 2026.
Which products and versions are affected?
myCred through 4.0.2.
Is there a fix for CVE-2026-123471?
Yes: fixed in 4.0.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-123471 attacked?
It is attacked over the network.
Am I affected by CVE-2026-123471?
Check whether you run myCred at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 4.0.3

Technical details

A stored XSS vulnerability exists in myCred through version 4.0.2 due to improper neutralization of HTML tags in user-supplied content. An attacker with subscriber privileges can inject script tags or other HTML content that persists on the site and executes in the browsers of other users viewing the affected pages. The vulnerability is classified as content injection with a CVSS score of 4.3.

Affected products

  • myCred myCred through 4.0.2

Timeline

  • 2026-11-06: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.