Quick answers
- Is CVE-2026-15150 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15150 being exploited in the wild.
- How severe is CVE-2026-15150?
- Medium severity, with a CVSS score of 5.3, published 21 August 2026.
- Which products and versions are affected?
- myCred before 3.2.5.
- Is there a fix for CVE-2026-15150?
- A patch was published on 2026-08-21: Fixed in version 3.2.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-15150 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-15150?
- 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.
Technical details
The vulnerability is a payment gateway notification validation bypass (CWE-346) in the myCred plugin's PayPal IPN handler. The buyCRED payment gateway accepts Instant Payment Notifications (IPN) from PayPal but fails to verify that the "receiver_email" or "business" field in the IPN matches the site's configured merchant account email. An unauthenticated attacker can initiate a purchase on the target site (which generates a pending purchase with a public ID), then send a crafted IPN from their own PayPal account with the same purchase ID and correct transaction amount, causing the site to credit the currency as if payment was received. The attack is network-accessible and requires no authentication; the attacker only needs their own PayPal account. Fixed in version 3.2.5; versions 3.2.3 and 3.2.4 reverted the original fix from 3.2.2.
Affected products
- myCred myCred before 3.2.5
Timeline
- 2026-08-17: disclosed
- 2026-08-21: patched: Fixed in version 3.2.5