# CVE-2026-122668: myCred broken access control in user permissions

Source: https://junglewise.ai/threats/cve-2026-122668-missing-authorization-vulnerability-in-mycred-mycred-mycred  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-07. Updated: 2026-11-07  
License: CC BY 4.0 with a link back

CVE-2026-122668 · Severity: medium · CVSS 4.3 · Published 2026-11-07

myCred is a gamification and reputation system plugin for WordPress that manages user points and achievements. This broken access control vulnerability allows subscribers to view or perform actions restricted to higher-privilege users, potentially exposing private user data or allowing unauthorized modifications.

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

## Quick answers

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

**How severe is CVE-2026-122668?** Medium severity, with a CVSS score of 4.3, published 7 November 2026.

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

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

**Am I affected by CVE-2026-122668?** 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 broken access control flaw in myCred allows users with lower privileges (e.g., Subscriber role) to access pages or perform actions intended for higher-privilege users by bypassing proper permission checks. The vulnerability affects versions up to 4.0.2 and requires only subscriber-level access to exploit. Version 4.0.3 and later fix the issue.

## Affected products

- myCred myCred through 4.0.2

## Timeline

- 2026-11-07: disclosed

## References

- [https://wordpress.org/plugins](https://wordpress.org/plugins)
- [https://patchstack.com/database/wordpress/plugin/mycred/vulnerability/wordpress-mycred-plugin-4-0-2-broken-access-control-vulnerability-5?_s_id=cve](https://patchstack.com/database/wordpress/plugin/mycred/vulnerability/wordpress-mycred-plugin-4-0-2-broken-access-control-vulnerability-5?_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 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)