# CVE-2026-97072: myCred broken access control in permission system

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

CVE-2026-97072 · Severity: medium · CVSS 4.3 · Published 2026-11-03

myCred is a WordPress plugin for managing user points and gamification. This vulnerability allows subscribers to view content or perform actions they should not be permitted, due to misconfigured access controls. An attacker with a basic account could potentially access restricted functionality or data intended only for administrators or specific user roles.

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

## Quick answers

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

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

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

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

**Am I affected by CVE-2026-97072?** 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 vulnerability in myCred allows users with Subscriber privilege to bypass permission checks and access resources or perform actions outside their authorization level. The vulnerability affects the access control security configuration in versions through 4.0.2. Exploitation requires user authentication but no special preconditions beyond a standard subscriber account.

## Affected products

- myCred myCred through 4.0.2

## Timeline

- 2026-09-20: disclosed: Vulnerability reported to Patchstack
- 2026-11-03: advisory: Published by Patchstack

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