CVE-2024-11979
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 · uneditedDreamMaker from Interinfo has a Path Traversal vulnerability and does not restrict the types of uploaded files. This allows unauthenticated remote attackers to upload arbitrary files to any directory, leading to arbitrary code execution by uploading webshells.
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 · high confidenceDreamMaker from Interinfo contains a path traversal vulnerability combined with unrestricted file upload functionality. This allows unauthenticated remote attackers to upload arbitrary files to any directory on the server, enabling deployment of webshells and resulting in arbitrary code execution.
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 DreamMaker installationLocate DreamMaker installation directories and identify the version number from the application binaries, configuration files, or application metadataAffected if DreamMaker is installed and the version falls within any affected version range
-
Identify the file upload functionalityLocate the file upload handler, controller, or endpoint within the DreamMaker application code - typically found in modules handling project file imports or asset uploadsAffected if The file upload module exists and is accessible without authentication
-
Verify file type restrictions are enforcedInspect the upload handler code or configuration to determine if MIME type, extension, or content validation is implemented for uploaded filesAffected if No file type restrictions exist or they can be easily bypassed
-
Check for path traversal protectionExamine the file upload code for path normalization, canonical path resolution, or directory traversal prevention logic when handling upload destination pathsAffected if Path traversal protection is absent or insufficient in the upload handling logic
-
Confirm upload directory is web-accessibleDetermine whether the configured upload directory is served by the web server and allows execution of uploaded file typesAffected if Uploaded files are stored in web-accessible directories with executable permissions
The environment is affected if DreamMaker is installed, the unauthenticated file upload functionality is exposed, and neither path traversal protection nor strict file type restrictions are enforced on uploads.
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 path traversal protection using canonical path resolution and whitelist validation, and restrict uploaded file types to only safe, non-executable formats with thorough extension and MIME type validation.
- 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-11979 — 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-11979 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