Quick answers
- Is CVE-2026-123465 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123465 being exploited in the wild.
- How severe is CVE-2026-123465?
- High severity, with a CVSS score of 7.5, published 9 November 2026.
- Which products and versions are affected?
- myCred through 4.0.2.
- Is there a fix for CVE-2026-123465?
- 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-123465 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-123465?
- 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 myCred plugin versions through 4.0.2 contain a sensitive data exposure vulnerability that allows unauthenticated network attackers to retrieve embedded sensitive information. The vulnerability requires no user interaction or privileges, making it trivially exploitable. An attacker can access private data including passwords, email addresses, and payment details.
Affected products
- myCred myCred through 4.0.2
Timeline
- 2026-10-23: disclosed: Reported to Patchstack
- 2026-11-07: advisory: Published on Patchstack
- 2026-11-07: patched: Version 4.0.3 released