Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-48287

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Deserialization of Untrusted Data vulnerability in Pagaleve Pix 4x sem juros - Pagaleve wc-pagaleve allows Object Injection.This issue affects Pix 4x sem juros - Pagaleve: from n/a through <= 1.6.9.

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 · moderate confidence

This is a PHP Object Injection vulnerability in the Pagaleve WooCommerce plugin (wc-pagaleve). The plugin deserializes untrusted data without proper validation, allowing attackers to inject malicious PHP objects. This can potentially lead to remote code execution, file deletion, or SQL injection depending on available magic methods in the application context.

MitigationUpdate the Pagaleve plugin to a version beyond 1.6.9 as soon as a patched release is available. If no patch is available, disable the plugin until a fix is released.

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

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
High
Availability
High

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

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. Check if Pagaleve plugin is installed
    Navigate to WordPress admin > Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'wc-pagaleve' or similar Pagaleve-related plugin
    Affected if The plugin is not installed
  2. Verify the installed version
    Check the plugin header in the main PHP file (usually wc-pagaleve.php) or view the version on the WordPress plugins page. Compare against the affected range: version 1.6.9 and below
    Affected if Version is 1.6.9 or lower
  3. Search for unsafe unserialize calls
    Use grep or a file search to look for 'unserialize' within the plugin directory. Focus on calls that process input from $_GET, $_POST, $_COOKIE, request parameters, or database values
    Affected if Any unserialize() calls are found that handle untrusted user input
  4. Identify exposed entry points
    Examine the plugin source code for AJAX action handlers, REST API routes, webhook callbacks, or form processing code that receive external data and pass it to unserialize()
    Affected if Exposed endpoints accept and deserialize data from untrusted sources

The environment is affected if the Pagaleve wc-pagaleve plugin version 1.6.9 or lower is installed and contains unsafe unserialize() calls that process untrusted input from external sources.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Pagaleve plugin to a version beyond 1.6.9 as soon as a patched release is available. If no patch is available, disable the plugin until a fix is released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2025-48287 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