CVE-2025-31087
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 silverplugins217 Multiple Shipping And Billing Address For Woocommerce different-shipping-and-billing-address-for-woocommerce allows Object Injection.This issue affects Multiple Shipping And Billing Address For Woocommerce: from n/a through <= 1.5.
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 confidenceThe plugin 'Multiple Shipping And Billing Address For WooCommerce' contains a PHP Object Injection vulnerability caused by unsafe use of unserialize() on untrusted input. An attacker can inject malicious PHP objects, potentially triggering magic methods to achieve remote code execution if gadget chains exist in the WordPress environment.
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.
-
Locate the plugin installationCheck for the presence of the 'Multiple Shipping And Billing Address For WooCommerce' plugin in the WordPress wp-content/plugins directory, or query it via WP-CLI: wp plugin list --name='multiple-shipping-and-billing-address-for-woocommerce'Affected if The plugin is not installed on the WordPress site
-
Identify the installed versionCheck the plugin's main PHP file header for the Version comment, or run: wp plugin get multiple-shipping-and-billing-address-for-woocommerce --field=versionAffected if The installed version matches or falls within the vulnerable version range (compare your version to the affected versions stated in the plugin's changelog or security advisory)
-
Find unsafe unserialize() calls in plugin codeSearch the plugin directory for unserialize() calls: grep -r "unserialize" /path/to/wp-content/plugins/multiple-shipping-and-billing-address-for-woocommerce/Affected if The plugin code contains unserialize() calls that process input without sanitization
-
Determine if untrusted input reaches unserialize()Examine the code around each unserialize() call to trace whether $_GET, $_POST, $_REQUEST, or similar user-supplied data flows into it. Look for patterns like unserialize($_POST['...']) or unserialize($_REQUEST['...'])Affected if User-controllable data from request parameters is passed directly to unserialize() without prior validation or sanitization
A user is affected if the plugin is installed, contains the vulnerable unserialize() pattern, and untrusted request input reaches that unserialize() call without validation.
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 dataReplace all unserialize() calls with json_decode() or implement proper input validation/whitelisting. Audit for and remove any dangerous magic methods in the plugin or dependent code that could be chained for RCE.
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31087 — 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-31087 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