CVE-2025-48287
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 · uneditedDeserialization 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 confidenceThis 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.
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 checksWork through these to decide whether this CVE applies to you.
-
Check if Pagaleve plugin is installedNavigate to WordPress admin > Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'wc-pagaleve' or similar Pagaleve-related pluginAffected if The plugin is not installed
-
Verify the installed versionCheck 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 belowAffected if Version is 1.6.9 or lower
-
Search for unsafe unserialize callsUse 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 valuesAffected if Any unserialize() calls are found that handle untrusted user input
-
Identify exposed entry pointsExamine 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.
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 dataUpdate 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.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48287 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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