Skip to content
Fencer Intel
medium 6.5

CVE-2026-42752 json

WordPress Stripe Payments plugin <= 2.0.98 - Bypass Vulnerability vulnerability

published 4mo ago modified 15d ago also EUVD-2026-36838

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits
0
none known

Summary

Unauthenticated Bypass Vulnerability in Stripe Payments <= 2.0.98 versions.

Patch / fix

  • mra13 / Team Tips and Tricks HQ Stripe Payments 2.0.99

Is CVE-2026-42752 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
4mo ago

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected products

  • mra13 / Team Tips and Tricks HQ Stripe Payments

Classification

Weakness
  • CWE-440 Expected Behavior Violation
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.