ZippyWordPress extension · Gesundheit Bewegt
CVE-2024-27964
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in Gesundheit Bewegt GmbH Zippy.This issue affects Zippy: from n/a through 1.6.9.
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 an unrestricted file upload vulnerability in Zippy (version 1.6.9 and earlier) that allows users to upload dangerous file types without proper validation. Attackers could upload malicious executables or scripts that may lead to remote code execution when accessed.
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.10CVSS 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.
-
Check installed Zippy versionLocate the Zippy application files and identify the version number from the codebase (typically in a version file, composer.json, or application metadata). Compare this version against the affected range (1.6.9 and earlier).Affected if The installed version is 1.6.9 or earlier, or the version cannot be determined and the application is known to be Zippy.
-
Identify if file upload functionality existsSearch the codebase for file upload handlers, forms, or endpoints that accept file submissions. Look for $_FILES usage, multipart form handling, or upload-related functions.Affected if File upload functionality is present and accessible to users.
-
Examine file type validation logicInspect the upload handling code to determine what file type validation (if any) is performed. Look for MIME type checks, file extension validation, or content analysis.Affected if No file type validation exists, or validation relies solely on file extensions or client-provided MIME types without verification.
-
Check upload directory configurationReview the web server and application configuration to determine where uploaded files are stored relative to the web root.Affected if Uploaded files are stored within the web-accessible directory tree.
-
Verify script execution restrictionsCheck the web server configuration (e.g., .htaccess, nginx config) for the upload directory to see if script execution is disabled.Affected if No restrictions are in place to prevent execution of uploaded files (e.g., no handler directives blocking PHP, Python, or other script types).
The environment is affected if Zippy version 1.6.9 or earlier is installed and the file upload feature is enabled without proper server-side file type validation and script execution restrictions.
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.
dbcve · scoped1.6.10
Implement strict allowlist-based file type validation, verify file magic bytes, store uploads outside the web root with randomized filenames, and disable script execution in upload directories.
Zippy 1.6.10
- Upgrade Zippy from any version below 1.6.10 to version 1.6.10 or later
Generated from the published advisory — verify against the referenced sources before acting.
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-2024-27964 — 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-2024-27964 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