dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-64227

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-18
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 BoldGrid Client Invoicing by Sprout Invoices sprout-invoices allows Object Injection.This issue affects Client Invoicing by Sprout Invoices: from n/a through <= 20.8.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 confidence

This is a PHP Object Injection vulnerability in the BoldGrid Client Invoicing (Sprout Invoices) WordPress plugin. The plugin deserializes untrusted data without proper validation, allowing attackers to inject malicious PHP objects that could lead to remote code execution, file deletion, or other attacks via crafted serialized payloads.

MitigationUpdate the plugin to the latest patched version as soon as available. If no patch exists, consider disabling or removing 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. Verify plugin installation
    Check if the BoldGrid Client Invoicing (formerly Sprout Invoices) plugin is present in your WordPress installation. Navigate to wp-content/plugins/ and look for directories named 'boldgrid-client-invoicing', 'sprout-invoices', or similar variants. Alternatively, check via WordPress admin under Plugins > Installed Plugins.
    Affected if The plugin directory exists in wp-content/plugins/
  2. Identify installed plugin version
    Open the main plugin PHP file (usually named plugin-name.php in the plugin directory) and locate the version comment or Version header in the plugin file header. For command-line, you can grep: grep -r 'Version:' wp-content/plugins/*/plugin-name.php | grep -i invoic
    Affected if The version displayed is lower than the patched version or cannot be determined (plugin is unmaintained)
  3. Confirm plugin is active
    Check WordPress admin under Plugins > Installed Plugins to verify if the BoldGrid Client Invoicing or Sprout Invoices plugin is currently activated. Alternatively, query the wp_options table: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins';
    Affected if The plugin appears in the active plugins list
  4. Verify PHP unserialize is in use (optional context)
    Review plugin source code for use of unserialize() function on user-supplied data. Search plugin files: grep -r 'unserialize' wp-content/plugins/boldgrid-client-invoicing/ or similar path.
    Affected if The plugin code contains unserialize() calls processing external input without prior validation

Your environment is affected if the BoldGrid Client Invoicing or Sprout Invoices plugin is installed, active, and running a version that has not been patched for the PHP Object Injection vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest patched version as soon as available. If no patch exists, consider disabling or removing the plugin until a fix is released.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (after 20.8.7)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate 'BoldGrid Client Invoicing by Sprout Invoices' (sprout-invoices).
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. If no update appears in WordPress, manually download the latest version from the official WordPress plugin repository.
  6. 6. Deactivate the plugin, then delete the existing installation, then upload and activate the new version.
  7. 7. Verify the plugin is functioning correctly by testing invoice creation and viewing.
  8. 8. Monitor the site for any unusual behavior after the update.
Caveat Review plugin settings and test any custom integrations after upgrading

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64227 — 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-2025-64227 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