# CVE-2026-114698: myCred authorization bypass in access control

Source: https://junglewise.ai/threats/cve-2026-114698-authorization-bypass-through-user-controlled-key-vulnerability  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-22. Updated: 2026-10-22  
License: CC BY 4.0 with a link back

CVE-2026-114698 · Severity: medium · CVSS 5.4 · Published 2026-10-22

myCred is a WordPress plugin that manages user gamification and reputation systems. An authorization bypass vulnerability allows attackers with subscriber-level access to view or manipulate data belonging to other users by modifying identifiers in URLs, potentially exposing sensitive user information or account details.

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

## Quick answers

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

**How severe is CVE-2026-114698?** Medium severity, with a CVSS score of 5.4, published 22 October 2026.

**Which products and versions are affected?** myCred through 4.0.0-beta.1.

**Is there a fix for CVE-2026-114698?** Yes: fixed in 4.0.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-114698 attacked?** It is attacked over the network, in a software library.

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

## Technical details

An Insecure Direct Object Reference (IDOR) vulnerability in myCred allows subscribers to bypass access controls by manipulating object references (typically user IDs) in requests. The vulnerability exists through version 4.0.0-beta.1 and has been fixed in version 4.0.0. The attack requires valid subscriber-level authentication and network access to the WordPress site.

## Affected products

- myCred myCred through 4.0.0-beta.1

## Timeline

- 2026-08-30: disclosed: Reported to Patchstack
- 2026-10-22: advisory: Published by Patchstack and NVD

## References

- [https://wordpress.org/plugins](https://wordpress.org/plugins)
- [https://patchstack.com/database/wordpress/plugin/mycred/vulnerability/wordpress-mycred-plugin-4-0-0-beta-1-insecure-direct-object-references-idor-vulnerability?_s_id=cve](https://patchstack.com/database/wordpress/plugin/mycred/vulnerability/wordpress-mycred-plugin-4-0-0-beta-1-insecure-direct-object-references-idor-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)