dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-68853

HIGH · 8.8 CVSS v3.1 Published 2026-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Kleor Contact Manager contact-manager allows Object Injection.This issue affects Contact Manager: from n/a through <= 9.1.1.

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

A PHP Object Injection vulnerability exists in Kleor Contact Manager due to unsafe deserialization of untrusted data. Attackers can potentially exploit this to execute arbitrary code by injecting malicious PHP objects, especially if magic methods exist in the application or installed plugins/themes.

MitigationReplace all unserialize() calls with safer alternatives like JSON encoding, implement strict input validation, and ensure no dangerous magic methods or pop chains exist in the codebase.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Confirm Kleor Contact Manager installation
    Search your web server file system for the Kleor Contact Manager plugin or module directory
    Affected if The Kleor Contact Manager software is present in your environment
  2. Locate PHP files using unserialize()
    Search the Kleor PHP source files for calls to the unserialize() function, particularly those processing data from $_GET, $_POST, $_COOKIE, or database query results
    Affected if unserialize() calls exist in the codebase without prior validation
  3. Identify magic method definitions
    Search the PHP files for magic method definitions such as __wakeup, __destruct, __toString, __get, __set, or __call that could be leveraged in a POP chain
    Affected if Dangerous magic methods exist in the application or its installed plugins/themes
  4. Check if external input reaches unserialize()
    Trace the data flow from user-supplied sources (request parameters, uploaded files, database fields) to the unserialize() calls identified
    Affected if Untrusted or unsanitized external data is passed directly to unserialize()

Your environment is affected if Kleor Contact Manager is installed AND contains unserialize() calls that process untrusted input, especially when dangerous magic methods are present in the codebase that could enable code execution.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace all unserialize() calls with safer alternatives like JSON encoding, implement strict input validation, and ensure no dangerous magic methods or pop chains exist in the codebase.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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