# CVE-2026-124274: myCred broken access control in authorization checks

Source: https://junglewise.ai/threats/cve-2026-124274-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-124274 · Severity: medium · CVSS 5.3 · Published 2026-11-07

myCred is a WordPress plugin that manages user points, badges, and gamification features. A broken access control vulnerability allows subscribers to access pages and perform actions they should not be permitted to, potentially exposing other users' data or functionality. The vulnerability affects versions up to 4.0.2 and is fixed in version 4.0.3.

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

## Quick answers

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

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

**Which products and versions are affected?** myCred up to 4.0.2.

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

**Am I affected by CVE-2026-124274?** 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 that allows users with subscriber-level privileges to bypass authorization checks and access restricted pages or perform restricted actions. The issue stems from improperly configured access control security levels. This is fixed in version 4.0.3.

## Affected products

- myCred myCred up to 4.0.2

## Timeline

- 2026-08-26: disclosed: Reported to Patchstack
- 2026-11-07: 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-4?_s_id=cve](https://patchstack.com/database/wordpress/plugin/mycred/vulnerability/wordpress-mycred-plugin-4-0-2-broken-access-control-vulnerability-4?_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 stored XSS via content injection](https://junglewise.ai/threats/cve-2026-123471-improper-neutralization-of-script-related-html-tags-in-a-web)