WordPress myCred plugin <= 4.0.2 - Sensitive Data Exposure vulnerability
- Exploited
- No known exploitation
- Fix
- Fixed in 4.0.3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.0.3.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 28/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
The WordPress myCred plugin, a points and rewards add-on, contains a flaw that exposes sensitive system information. An attacker can remotely retrieve that embedded data without logging in.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in myCred myCred mycred allows Retrieve Embedded Sensitive Data.This issue affects myCred: from n/a through 4.0.2.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 4.0.3.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- mycred
through 4.0.2
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123465
Is CVE-2026-123465 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The flaw can expose private information such as passwords, email addresses, or payment details to unauthorized parties.Source: patchstack.com, cve.org
Which versions are affected by CVE-2026-123465?
mycred: through 4.0.2.Source: cve.now feed data
Am I affected, and how do I check?
Versions of the myCred plugin up to and including 4.0.2 for WordPress are in the affected range, and no specific setup conditions are listed. To check the installed version, look at the plugin version shown on the WordPress Plugins page.Source: patchstack.com, cve.org
How do I fix CVE-2026-123465?
Update the myCred plugin to version 4.0.3 or later. The advisory recommends the latest available version, which must be at least 4.0.3.Source: patchstack.com, cve.org