dbcve.org
Soisy Pagamento RatealeWordPress extension · Soisy

CVE-2023-5132

HIGH · 7.5 CVSS v3.1 Published 2023-10-21
Fix available
A fix is available. Upgrade to after 6.0.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Soisy Pagamento Rateale WordPress plugin lacks a capability check on the parseRemoteRequest function, enabling unauthenticated attackers to retrieve sensitive WooCommerce order details (customer name, address, email, and metadata) by simply knowing a valid order ID. This is a broken access control (IDOR) vulnerability.

MitigationUpdate the plugin to version 6.0.2 or later which includes proper capability checks on the parseRemoteRequest function. Until then, consider disabling the plugin or restricting access to the vulnerable endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Soisy Pagamento RatealeWordPress extension
Affected:<= 6.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the Soisy Pagamento Rateale plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'Soisy Pagamento Rateale' or 'Soisy'. Alternatively, check the plugin directory /wp-content/plugins/ for a folder containing 'soisy'.
    Affected if The plugin is installed and active.
  2. Check the installed plugin version
    In WordPress admin, find the Soisy Pagamento Rateale plugin in the Plugins list and look at the version number displayed below the plugin name. Alternatively, check the main plugin PHP file for the 'Version' header in the plugin comments.
    Affected if The installed version is 6.0.1 or lower.
  3. Confirm WooCommerce is active
    In WordPress admin, go to Plugins > Installed Plugins and verify WooCommerce is installed and active. This plugin depends on WooCommerce to expose order data.
    Affected if WooCommerce is active alongside the vulnerable plugin version.
  4. Check for unauthenticated access attempts to the vulnerable endpoint
    Review web server access logs (Apache/nginx) for requests to the Soisy plugin's endpoint. Look for HTTP GET or POST requests containing 'order_id' or similar parameters targeting the parseRemoteRequest function without authentication tokens.
    Affected if Unauthenticated requests to order-related endpoints with order IDs are being logged.

A user is affected if the Soisy Pagamento Rateale plugin version 6.0.1 or lower is installed and active alongside WooCommerce, allowing unauthenticated access to order data via the parseRemoteRequest function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 6.0.1
Interim mitigation

Update the plugin to version 6.0.2 or later which includes proper capability checks on the parseRemoteRequest function. Until then, consider disabling the plugin or restricting access to the vulnerable endpoint.

Recommended fix Moderate confidence

Soisy Pagamento Rateale version 6.0.2 or latest stable release

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Soisy Pagamento Rateale' plugin
  4. Check if an update to version 6.0.2 or higher is available
  5. If an update is available, click 'Update Now' to install the fixed version
  6. If no update is available through the WordPress admin, download the latest version from the WordPress Plugin Repository and upload/install it manually
  7. Verify the plugin updated successfully to version 6.0.2 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Soisy Pagamento Rateale Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-5132 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-5132 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data