CVE-2026-15150
MediumCVSS 5.3Exploitation Probability (EPSS)
Low risk2th percentile - higher than 2% of all known CVEs
Summary
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.
Risk Assessment
The risk includes the possibility of unauthorized crediting of accounts with in-site currency, which may lead to abuse and financial losses.
Recommendation
It is recommended to update the myCred plugin to version 3.2.5 or later and implement receiver verification for notifications.
Other vulnerabilities in myCred
See all- CVE-2026-61968Medium
The myCred WordPress plugin contains a missing authorization vulnerability that allows exploiting incorrectly configured access control security levels. This issue affects versions up to and including 3.1.2.
- CVE-2026-40794Medium
Versions of myCred up to 3.0.3 have a vulnerability in access control, allowing unauthorized access to subscriber resources.
- CVE-2026-42676Medium
The myCred plugin is vulnerable to Stored Cross-Site Scripting (XSS) in all versions up to and including 3.0.4. Improper neutralization of input during web page generation allows attackers to inject malicious scripts that are then executed in other users' browsers.
Original NVD description (English source)
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.