dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-60216

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-22
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 BoldThemes Addison addison allows Object Injection.This issue affects Addison: from n/a through < 1.4.8.

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

The BoldThemes Addison WordPress theme before version 1.4.8 is vulnerable to PHP Object Injection via deserialization of untrusted data. Attackers can exploit this by supplying serialized PHP objects to unserialize() calls, potentially achieving remote code execution, file operations, or SQL injection depending on available gadget chains.

MitigationUpdate the Addison theme to version 1.4.8 or later to apply the vendor patch. If immediate updating is not feasible, consider disabling the theme or implementing Web Application Firewall rules to detect deserialization payloads.

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. Locate the Addison theme files
    Check the WordPress themes directory at wp-content/themes/addon/ or wp-content/themes/boldthemes-addon/ for the presence of the Addison theme folder.
    Affected if The Addison theme folder does not exist in the themes directory.
  2. Find the theme version
    Open the style.css file in the theme folder and locate the 'Version:' header in the file comment block, or check theme.json for the 'version' field.
    Affected if Unable to locate a version declaration in the theme files.
  3. Compare version to the affected range
    Compare the installed version against 1.4.8. Versions prior to 1.4.8 (such as 1.4.7, 1.4.6, etc.) are affected.
    Affected if The installed version is a version number less than 1.4.8 (for example, 1.4.7, 1.4.5, 1.0.0).
  4. Confirm the theme is active
    In the WordPress admin dashboard, go to Appearance > Themes to verify whether the Addison theme is currently activated on the site.
    Affected if The Addison theme is the active theme on the WordPress site.
  5. Identify deserialization entry points
    Search theme PHP files for functions that handle unserialize(), particularly in AJAX handlers, form processing files, or custom REST API endpoints within the theme folder.
    Affected if Theme files contain unserialize() calls processing external input without validation.

A WordPress site is affected if the BoldThemes Addison theme version is less than 1.4.8 and the theme is installed and active on the site.

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 Addison theme to version 1.4.8 or later to apply the vendor patch. If immediate updating is not feasible, consider disabling the theme or implementing Web Application Firewall rules to detect deserialization payloads.

Recommended fix High confidence

Addison version 1.4.8 or higher

  1. 1. Backup your WordPress site database and files before making any changes
  2. 2. Navigate to Appearance > Themes in the WordPress admin dashboard
  3. 3. Locate the Addison theme and check for available updates
  4. 4. Update the Addison theme to version 1.4.8 or the latest available version
  5. 5. Verify the update was successful by checking the theme version in WordPress admin
  6. 6. Test critical site functionality to ensure the update did not break existing features
  7. 7. If using a child theme, verify it remains compatible with the updated parent theme

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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