# CVE-2026-123465: myCred WordPress plugin sensitive data exposure

Source: https://junglewise.ai/threats/cve-2026-123465-exposure-of-sensitive-system-information-to-an-unauthorized  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-09. Updated: 2026-11-09  
License: CC BY 4.0 with a link back

CVE-2026-123465 · Severity: high · CVSS 7.5 · Published 2026-11-09

myCred is a WordPress plugin that manages gamification and user engagement features. This vulnerability allows unauthorized attackers to retrieve sensitive data such as passwords, emails, or payment details from the plugin without authentication. Exploitation requires no special skills and poses a high risk to any WordPress site running the affected plugin.

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

## Quick answers

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

**How severe is CVE-2026-123465?** High severity, with a CVSS score of 7.5, published 9 November 2026.

**Which products and versions are affected?** myCred through 4.0.2.

**Is there a fix for CVE-2026-123465?** 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-123465 attacked?** It is attacked over the network.

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

The myCred plugin versions through 4.0.2 contain a sensitive data exposure vulnerability that allows unauthenticated network attackers to retrieve embedded sensitive information. The vulnerability requires no user interaction or privileges, making it trivially exploitable. An attacker can access private data including passwords, email addresses, and payment details.

## Affected products

- myCred myCred through 4.0.2

## Timeline

- 2026-10-23: disclosed: Reported to Patchstack
- 2026-11-07: advisory: Published on Patchstack
- 2026-11-07: patched: Version 4.0.3 released

## References

- [https://wordpress.org/plugins](https://wordpress.org/plugins)
- [https://patchstack.com/database/wordpress/plugin/mycred/vulnerability/wordpress-mycred-plugin-4-0-2-sensitive-data-exposure-vulnerability?_s_id=cve](https://patchstack.com/database/wordpress/plugin/mycred/vulnerability/wordpress-mycred-plugin-4-0-2-sensitive-data-exposure-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 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)
- [myCred stored XSS via content injection](https://junglewise.ai/threats/cve-2026-123471-improper-neutralization-of-script-related-html-tags-in-a-web)