CVE-2023-5132 json
Soisy Pagamento Rateale <= 6.0.1 - Missing Authorization to Sensitive Information Exposure
published 3y ago modified 5mo ago also EUVD-2023-57470
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
The Soisy Pagamento Rateale plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the parseRemoteRequest function in versions up to, and including, 6.0.1. This makes it possible for unauthenticated attackers with knowledge of an existing WooCommerce Order ID to expose sensitive WooCommerce order information (e.g., Name, Address, Email Address, and other order metadata).
Is CVE-2023-5132 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.77% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-22).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- soisytech Soisy Pagamento Rateale
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
-
wordfence.com
/threat-intel/vulnerabilities/id/d3c997cd-37b4-4b9c-b99e-397be484aa36?source=cve
third-party-advisory
-
plugins.trac.wordpress.org
/browser/soisy-pagamento-rateale/trunk/public/class-soisy-pagamento-rateale-public.php#L465
product
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=2979568%40soisy-pagamento-rateale&new=2979568%40soisy-pagamento
Sources
- CVE List CVE-2023-5132
- NVD CVE-2023-5132
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.