Is CVE-2026-8607 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-8607 being exploited in the wild.

How severe is CVE-2026-8607?

Medium severity, with a CVSS score of 6.4, published 17 June 2026.

Which products and versions are affected?

myCred up to, and including, 3.1.

Is there a fix for CVE-2026-8607?

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-8607 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-8607?

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.

CVE-2026-8607: myCred WordPress plugin Stored XSS in wrap shortcode attribute

CVE-2026-8607 · Severity: medium · CVSS 6.4 · Published 2026-06-17

The myCred plugin for WordPress, which manages loyalty points and rewards, is vulnerable to a security flaw that allows certain users to inject malicious scripts into website pages. An attacker with contributor-level access or higher can use this to target other users, including site administrators, potentially leading to unauthorized actions or data theft when those users view the affected pages. This could compromise the integrity of the rewards program and the security of site visitors.

Technologies: myCred. Vendors: myCred.

Quick answers

Is CVE-2026-8607 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-8607 being exploited in the wild.
How severe is CVE-2026-8607?: Medium severity, with a CVSS score of 6.4, published 17 June 2026.
Which products and versions are affected?: myCred up to, and including, 3.1.
Is there a fix for CVE-2026-8607?: 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-8607 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-8607?: 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

The myCred plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) due to insufficient input sanitization and output escaping on the 'wrap' attribute within its shortcodes. Authenticated attackers with contributor-level permissions or higher can exploit this by injecting arbitrary web scripts into pages. These scripts execute in the context of any user's browser who visits the compromised page. The vulnerability is present in all versions up to and including 3.1. A patch appears to be available in subsequent versions (e.g., 3.1.1 or via changeset 3572451).

Affected products

saadiqbal myCred up to, and including, 3.1

Timeline

2026-06-17: disclosed
2026-06-17: advisory

References

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