dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-50507

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-30
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 Daschmi DS.DownloadList dsdownloadlist allows Object Injection.This issue affects DS.DownloadList: from n/a through <= 1.3.

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 deserialization of untrusted data vulnerability in Daschmi DS.DownloadList component allows attackers to inject malicious serialized objects, potentially leading to remote code execution. The vulnerability affects versions through 1.3.

MitigationUpdate to a patched version if available, otherwise implement strict input validation before deserialization and consider disabling PHP unserialize() in favor of json_decode() or similar safe parsing methods.

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. Confirm Daschmi DS installation
    Locate the Daschmi DS application on the system - look for the main application directory or check web server document roots for Daschmi DS files
    Affected if Daschmi DS is not installed on the system
  2. Check installed version
    Identify the installed version of Daschmi DS by examining version files, headers, or the application itself, then compare to the affected range (versions through 1.3)
    Affected if The installed version is 1.3 or any earlier version
  3. Verify DownloadList component presence
    Locate the DownloadList component within the Daschmi DS installation - check for files or modules related to DownloadList functionality
    Affected if The DownloadList component exists and is installed
  4. Check for vulnerable deserialization code
    Inspect the DownloadList component code for PHP unserialize() calls or similar deserialization functions that process untrusted input without validation
    Affected if The code contains deserialization logic handling user-supplied data without proper validation

A system is affected if Daschmi DS version 1.3 or earlier is installed with the DownloadList component, and that component contains deserialization code processing untrusted input.

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

Update to a patched version if available, otherwise implement strict input validation before deserialization and consider disabling PHP unserialize() in favor of json_decode() or similar safe parsing methods.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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