CVE-2025-49380
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 wpinstinct WooCommerce Vehicle Parts Finder woo-vehicle-parts-finder allows Object Injection.This issue affects WooCommerce Vehicle Parts Finder: from n/a through <= 3.7.
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 confidenceA deserialization vulnerability in the WooCommerce Vehicle Parts Finder WordPress plugin allows unauthenticated attackers to inject PHP objects through untrusted serialized data, potentially achieving remote code execution via object injection gadget chains.
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.
-
Confirm plugin installationNavigate to WordPress admin dashboard > Plugins and verify if 'WooCommerce Vehicle Parts Finder' is installed. Note the installed version if displayed.Affected if The plugin is installed and no patched version has been confirmed.
-
Identify plugin versionAccess the plugin files via FTP or file manager. Locate the main plugin file (commonly 'vehicle-parts-finder.php' or similar in /wp-content/plugins/) and find the version defined in the plugin header comment.Affected if The installed version is older than any patched version released for this vulnerability.
-
Locate vulnerable deserialization codeSearch the plugin directory for PHP files containing 'unserialize(' calls. Use grep or a file search tool to scan .php files within the plugin folder.Affected if Any PHP file in the plugin accepts user input and passes it to unserialize() without prior sanitization.
-
Verify input sourcesExamine the files containing unserialize() calls. Identify if the data being deserialized comes from user-controllable sources such as $_GET, $_POST, $_REQUEST, or database fields that could be manipulated by attackers.Affected if Untrusted user input reaches the unserialize() function.
-
Check plugin accessibilityReview the plugin's AJAX handlers or public endpoints listed in the plugin code. Determine if unauthenticated users can trigger the vulnerable deserialization code.Affected if The vulnerable code is accessible without authentication or via publicly reachable WordPress AJAX actions.
Your environment is affected if the WooCommerce Vehicle Parts Finder plugin is installed, contains unserialize() calls handling untrusted input, and you have not confirmed a patched version is in use.
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 to the latest patched version of the WooCommerce Vehicle Parts Finder plugin; if no patched version is available, disable the plugin until remediation is released.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49380 — 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-49380 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