CVE-2026-10072
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 developed by Interinfo has an Arbitrary File Upload vulnerability, allowing privileged remote attackers to upload and execute web shell backdoors, thereby enabling arbitrary code execution on the server.
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 confidenceDreamMaker by Interinfo contains an arbitrary file upload vulnerability that allows authenticated remote attackers to upload malicious files, including web shells, to the server. The uploaded files can then be executed, leading to arbitrary code execution on the underlying system. This is a critical file validation failure where the application does not properly validate file types, contents, or destination paths before accepting uploads.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Identify DreamMaker installation and versionLocate the DreamMaker installation directory and check for version information in the application files, configuration, or headers. Compare against any published version numbers from the vendor.Affected if DreamMaker is installed and the version falls within an affected range (if known) or cannot be determined.
-
Verify file upload feature is enabledAccess the DreamMaker admin or user interface and confirm whether file upload functionality exists and is accessible to authenticated users.Affected if File upload feature is enabled and accessible to authenticated privileged users.
-
Confirm authentication requirements for uploadsTest the file upload endpoint to determine if it requires authentication and what privilege level is needed to access it.Affected if The upload endpoint accepts requests from authenticated privileged users without additional authorization checks.
-
Inspect upload directory contentsExamine the directories where uploaded files are stored. Look for executable file types (php, asp, jsp, js, exe, sh, etc.) or files with double extensions.Affected if Executable or suspicious file types are present in upload directories, especially files that were not intentionally uploaded by administrators.
-
Check server script execution settingsReview web server configuration (Apache, Nginx, IIS) to determine if script execution is allowed in the upload directory path.Affected if Script execution is enabled in the upload directory and files are stored within the webroot.
A user is affected if DreamMaker is installed, the file upload feature is accessible to authenticated privileged users, and executable files can be uploaded and executed from the webroot.
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 allow-list based file type validation, verify file content (magic bytes) rather than just extensions, store uploaded files outside the web root, and disable script execution in upload directories. Additionally, enforce proper authentication and authorization for upload functionality.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10072 — 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-2026-10072 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