# CVE-2026-97073: myCred broken access control in plugin

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

CVE-2026-97073 · Severity: medium · CVSS 5.3 · Published 2026-10-29

The myCred WordPress plugin, used for gamification and user engagement on WordPress sites, contains a broken access control vulnerability that allows unauthenticated users to access pages or perform actions they should not be permitted to perform. An attacker could view other users' data or perform unauthorized actions on the affected site without authentication.

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

## Quick answers

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

**How severe is CVE-2026-97073?** Medium severity, with a CVSS score of 5.3, published 29 October 2026.

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

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

**Am I affected by CVE-2026-97073?** 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 vulnerability is a broken access control issue in myCred versions through 4.0.2 that fails to properly restrict access to certain pages and functions. An unauthenticated attacker can exploit this to view other users' data or perform unauthorized actions. The issue is fixed in version 4.0.3.

## Affected products

- myCred myCred through 4.0.2

## Timeline

- 2026-09-21: disclosed: Reported to Patchstack
- 2026-10-29: 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?_s_id=cve](https://patchstack.com/database/wordpress/plugin/mycred/vulnerability/wordpress-mycred-plugin-4-0-2-broken-access-control-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)