# CVE-2026-42676: myCred Stored Cross-Site Scripting in WordPress plugin

Source: https://junglewise.ai/threats/cve-2026-42676-mycred-stored-cross-site-scripting-in-wordpress-plugin  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-01. Updated: 2026-06-01  
License: CC BY 4.0 with a link back

CVE-2026-42676 · Severity: medium · CVSS 6.5 · Published 2026-06-01

myCred is a popular WordPress plugin used to manage loyalty programs and points systems. A security flaw allows an attacker with basic user permissions to inject malicious scripts into the website. If an administrator or another visitor views the affected page, the script could redirect them to malicious sites, steal session information, or display unauthorized advertisements.

Technologies: [myCred](https://junglewise.ai/threats/technologies/mycred). Vendors: [myCred](https://junglewise.ai/threats/vendors/mycred).

## Quick answers

**Is CVE-2026-42676 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-42676 being exploited in the wild.

**How severe is CVE-2026-42676?** Medium severity, with a CVSS score of 6.5, published 1 June 2026.

**Which products and versions are affected?** myCred up to 3.0.4.

**Is there a fix for CVE-2026-42676?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-42676 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-42676?** 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.

## Technical details

A Stored Cross-Site Scripting (XSS) vulnerability exists in the myCred plugin for WordPress (versions up to 3.0.4) due to improper neutralization of user-supplied input during web page generation (CWE-79). An attacker with 'Subscriber' or higher privileges can inject malicious JavaScript payloads that are permanently stored on the server. The vulnerability is triggered when a privileged user, such as an administrator, interacts with the affected page or component. Successful exploitation can lead to session hijacking, unauthorized redirects, or modification of page content. The issue is resolved in version 3.0.5.

## Affected products

- myCred myCred up to 3.0.4

## Timeline

- 2026-04-15: other: Reported by thevietronin
- 2026-05-15: advisory: Patchstack advisory published
- 2026-06-01: disclosed: CVE published to NVD

## References

- [https://patchstack.com/database/wordpress/plugin/mycred/vulnerability/wordpress-mycred-plugin-3-0-4-cross-site-scripting-xss-vulnerability?_s_id=cve](https://patchstack.com/database/wordpress/plugin/mycred/vulnerability/wordpress-mycred-plugin-3-0-4-cross-site-scripting-xss-vulnerability?_s_id=cve)

## Related threats

- [myCred content injection vulnerability](https://junglewise.ai/threats/cve-2026-125778-improper-neutralization-of-script-related-html-tags-in-a-web)
- [myCred WordPress plugin sensitive data exposure](https://junglewise.ai/threats/cve-2026-123465-exposure-of-sensitive-system-information-to-an-unauthorized)
- [myCred broken access control in WordPress plugin](https://junglewise.ai/threats/cve-2026-123462-missing-authorization-vulnerability-in-mycred-mycred-mycred)
- [myCred broken access control in user permissions](https://junglewise.ai/threats/cve-2026-122668-missing-authorization-vulnerability-in-mycred-mycred-mycred)
- [myCred broken access control in authorization checks](https://junglewise.ai/threats/cve-2026-124274-missing-authorization-vulnerability-in-mycred-mycred-mycred)