CVE-2026-131971 json
GetPaid 2.6.2 - 2.8.62 - Unauthenticated Invoice Disclosure via Payment Form Embed
published 22h ago modified 22h ago also EUVD-2026-132008
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
The Payment forms, Buy now buttons, and Invoicing System | GetPaid WordPress plugin before 2.8.63 does not check that the visitor is allowed to view an invoice before rendering it through its single-invoice shortcode, and its payment-form embed page lets unauthenticated users render that shortcode for any invoice ID, disclosing customers' names, billing addresses, phone numbers, line items and payment status.
Patch / fix
- Unknown Payment forms, Buy now buttons, and Invoicing System | GetPaid 2.8.63
Is CVE-2026-131971 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 FencerExploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-21).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/4b26e62a-29da-4b56-818e-aed7f439831e/ referenced PoC, tagged "exploit" by a source, unverified
Affected products
- Unknown Payment forms, Buy now buttons, and Invoicing System | GetPaid
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
- Technology feeds
References
-
wpscan.com
/vulnerability/4b26e62a-29da-4b56-818e-aed7f439831e/
exploit, vdb-entry, technical-description
Sources
- CVE List CVE-2026-131971
- NVD CVE-2026-131971
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.