ZippyWordPress extension · Gesundheit Bewegt
CVE-2023-36381
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 Gesundheit Bewegt GmbH Zippy.This issue affects Zippy: from n/a through 1.6.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 deserialization of untrusted data vulnerability in Zippy, a PHP library from Gesundheit Bewegt GmbH. The vulnerability affects versions up to 1.6.5, allowing attackers to potentially execute arbitrary code or cause denial of service by supplying malicious serialized data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ZippyWordPress extension
<= 1.6.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Locate Zippy library in your projectSearch for the Zippy package in your project's composer.json dependencies or check if the vendor/zippy-php/zippy directory existsAffected if Zippy library is present in the vendor directory or declared as a dependency
-
Determine installed Zippy versionRun 'composer show zippy-php/zippy' or check the version field in composer.lock for the zippy-php/zippy packageAffected if The installed version is 1.6.5 or any earlier version (1.x.x <= 1.6.5)
-
Identify if Zippy Archive::load or Archive::loadYaml is usedSearch your codebase for calls to \Zippy\Archive::load() or \Zippy\Archive::loadYaml() methods, especially where the archive source is user-controlled inputAffected if Your code calls Archive::load() or loadYaml() with data from untrusted sources (user input, external APIs, uploaded files)
-
Check for unsafe deserialization patternsReview code that handles Zippy operations - look for instances where untrusted data (uploaded archives, deserialized cache, external input) is passed directly to Zippy without prior validationAffected if Untrusted data flows into Zippy's deserialization without sanitization or JSON validation
You are affected if Zippy version 1.6.5 or earlier is installed AND untrusted data reaches Zippy's Archive loading methods.
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 dataUpgrade to a patched version of Zippy if available, or replace unsafe deserialization (unserialize()) with safer alternatives like JSON decoding with strict validation. If the vulnerable code processes external input, implement input validation and whitelisting before deserialization.
Fix this in Zippy
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36381 — 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-2023-36381 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