dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-32502

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-25
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 Select-Themes Borgholm borgholm-marketing-agency-theme allows Object Injection.This issue affects Borgholm: from n/a through < 1.6.

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

Object Injection vulnerability in the Borgholm WordPress theme allows remote attackers to inject malicious PHP objects through deserialization of untrusted data, potentially achieving arbitrary code execution. The vulnerability exists in the borgholm-marketing-agency-theme from unversioned releases through versions prior to 1.6.

MitigationUpdate the Borgholm theme to version 1.6 or later to receive the security patch. Until updated, disable the theme and audit all code paths that handle untrusted input, particularly any use of unserialize() or similar deserialization functions.

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 Borgholm theme installation
    Check your WordPress themes directory (wp-content/themes/) for a folder named 'borgholm' or 'borgholm-marketing-agency-theme'. If using a child theme, also check the parent theme directory.
    Affected if The Borgholm theme folder exists in your WordPress themes directory.
  2. Determine the installed theme version
    Open the theme's style.css file (usually at wp-content/themes/borgholm/style.css) and locate the 'Version:' comment in the file header. Alternatively, check theme.json or any version file bundled with the theme.
    Affected if The version is missing, unversioned, or shows a version number lower than 1.6.
  3. Search for deserialization functions in theme files
    Use grep or a file search tool to scan all PHP files in the Borgholm theme directory for calls to unserialize(), var_export(), or similar PHP deserialization functions. Review the context of each occurrence to see if it processes data from user input ($_GET, $_POST, $_REQUEST, or database fields).
    Affected if Any unserialize() or similar deserialization call processes input without prior sanitization or validation.
  4. Inspect theme for suspicious injected files
    Review all PHP files in the Borgholm theme directory. Compare the file list against a known-clean installation or the original theme package. Look for files with unusual names, recent modification dates, or encoded/obfuscated code content.
    Affected if New or modified PHP files exist that were not part of the original theme distribution.

You are affected if the Borgholm theme is installed and its version is prior to 1.6 or unversioned, particularly if the theme code contains unprotected deserialization of user-controlled data.

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 Borgholm theme to version 1.6 or later to receive the security patch. Until updated, disable the theme and audit all code paths that handle untrusted input, particularly any use of unserialize() or similar deserialization functions.

Recommended fix High confidence

Borgholm theme version 1.6 or later

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Appearance > Themes in your WordPress admin dashboard
  3. 3. Locate the Borgholm theme in your installed themes
  4. 4. Check the current version of the Borgholm theme
  5. 5. If the current version is below 1.6, update the theme to version 1.6 or later to remediate the deserialization vulnerability
  6. 6. Verify the theme update was successful by confirming the new version number
Caveat Review theme settings and customizations after upgrade as template changes may affect site appearance

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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