CVE-2025-60236
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 EMV Creatify allows Object Injection. This issue affects Creatify: from n/a through 1.5.
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 confidenceThis is a critical deserialization vulnerability in EMV Creatify where untrusted input is being deserialized without proper validation, allowing attackers to inject and instantiate arbitrary objects. Object Injection vulnerabilities of this severity often enable remote code execution through maliciously crafted serialized 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm EMV Creatify installationSearch for EMV Creatify in your application directory or check installed packages. Look for directories named 'emv-creatify', 'creatify', or check your package manager for emv-creatify entries.Affected if EMV Creatify software is not found in the environment, the system is not affected.
-
Determine installed versionLocate the version file or check the software's 'about' section. Common locations include: version.php, composer.json, package.json, or a README/version file in the product root directory. Run 'composer show emv-creatify' or 'npm list emv-creatify' if using a package manager.Affected if The installed version matches or falls within any affected version range provided by the vendor.
-
Identify deserialization endpointsSearch the codebase for functions that handle deserialization: look for unserialize(), json_decode(), pickle.loads(), yaml.load(), or similar deserialization methods. Check PHP, Java, Python, or Node.js code depending on the technology stack.Affected if The application deserializes untrusted input without validation - the vulnerability is present.
-
Audit input handling for user-supplied dataReview forms, API endpoints, file uploads, or web services that accept external data. Trace the data flow from input to any deserialization call. Look for parameters that accept serialized objects or complex data structures.Affected if User-controllable data reaches a deserialization function without sanitization or allowlist validation.
-
Check for unsafe deserialization configurationExamine configuration files and application settings for deserialization-related options. Look for flags like 'allowed_classes', 'unserialize_options', or similar settings that control what objects can be instantiated.Affected if No class allowlisting is configured, or the deserialization accepts any class type.
If EMV Creatify is installed and processes untrusted input through deserialization without class allowlisting or validation, the environment is likely affected by CVE-2025-60236.
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 dataImplement strict input validation and use safe deserialization practices such as allowlisting of permitted classes, avoiding native PHP/Java deserialization of untrusted data, or replacing with structured data formats like JSON with explicit type handling.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60236 — 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-60236 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