# CVE-2023-5132: Soisy Pagamento Rateale <= 6.0.1 - Missing Authorization to Sensitive Information Exposure

> Unauthenticated attackers can expose sensitive WooCommerce order data by exploiting a missing capability check in the Soisy Pagamento Rateale plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Oct 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-6jpv-f5xm-f87c

## What is CVE-2023-5132?

CVE-2023-5132 is a high-severity missing authorization vulnerability in soisytech Soisy Pagamento Rateale, published on 21 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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).

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2023-5132?

It affects 1 product.


Products: Soisy Soisy Pagamento Rateale.

## How do I fix CVE-2023-5132?

No fix has been published for CVE-2023-5132 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-5132 being exploited?

There is no known exploitation of CVE-2023-5132 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5132 and fix it if it is affected.

What it is: CVE-2023-5132 is a high-severity missing authorization vulnerability in soisytech Soisy Pagamento Rateale, published on 21 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-5132 in the wild and no public exploit code.

Affected product: soisytech Soisy Pagamento Rateale. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-5132/ (Markdown: https://insights.sbomify.com/CVE-2023-5132/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-5132
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-5132
- OSV: https://osv.dev/vulnerability/CVE-2023-5132

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-5132/
Summaries are generated and may contain mistakes; the official description above is the record.