myCred credits site currency for payments sent to an attacker-controlled account
myCred before 3.2.5 does not verify that the receiver named by an incoming payment-gateway notification matches the site's configured merchant account. An unauthenticated attacker can pay the expected amount to a gateway account they control and have an arbitrary amount of the site's in-site currency credited to an account.
- Component
- myCred
- Plugin slug
mycred- Affected
- < 3.2.5
- Safe version
3.2.5- Published
- Aug 21, 2026
This CVE was published Aug 21, 2026 and is one of 30 known issues for this plugin.
Update, patch or deactivate.
Update myCred to 3.2.5 or later. Reconcile gateway receipts against credited in-site currency, reverse fraudulent credits where appropriate and review accounts receiving unusual balance increases.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The myCred WordPress plugin before 3.2.5 does not verify that the receiver of an incoming payment gateway notification matches the site's configured merchant account, allowing unauthenticated attackers to have arbitrary amounts of the site's in-site currency credited to an account by completing a payment for the expected amount to a gateway account they control rather than the site's.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N