CVE-2026-15150: myCred (WordPress plugin) · Insufficient Verification of Data Authenticity
Affects myCred (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.2.5 when convenient.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.2.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade myCred (WordPress plugin) to 3.2.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| myCred | Affected
| Fixed in
|
AI-suggested
A fix is available in myCred version 3.2.5 and later. Site administrators should upgrade to version 3.2.5 or newer to remediate this vulnerability. No additional mitigation steps are indicated by the vendor advisory or CVE data.
Description
The myCred WordPress plugin versions before 3.2.5 contain a vulnerability where the plugin does not verify that the receiver of an incoming payment gateway notification matches the site's configured merchant account. This flaw allows unauthenticated attackers to credit arbitrary amounts of the site's in-site currency to an account by completing a payment to a gateway account they control instead of the legitimate merchant account.