CVE-2026-24729
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 · uneditedAn unrestricted upload of file with dangerous type vulnerability in the file upload function of Interinfo DreamMaker versions before 2025/10/22 allows remote attackers to execute arbitrary system commands via a malicious class file.
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 confidenceInterinfo DreamMaker suffers from an unrestricted file upload vulnerability in its file upload function. Attackers can upload malicious Java class files (.class) which, when accessed, allow arbitrary system command execution. The lack of proper file type validation and sanitization enables remote 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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 Interinfo DreamMaker installationLocate DreamMaker installation directory - check common paths like /var/www/html/, C:\inetpub\, or application-specific directories. Look for DreamMaker executable or configuration files.Affected if DreamMaker is present and the file upload feature is in use
-
Identify file upload functionalityExamine DreamMaker's web interface or configuration for file upload endpoints. Look for forms, APIs, or modules that handle file uploads.Affected if A file upload feature exists and is accessible to users
-
Check file type validation configurationInspect DreamMaker's configuration files, upload handlers, or security settings. Look for allowlist/denylist configurations for permitted file extensions.Affected if No file type validation exists or .class files are explicitly allowed in the upload configuration
-
Verify upload directory locationLocate the configured upload directory in DreamMaker's settings. Check if uploads are stored within the webroot or in a directory accessible via HTTP/HTTPS.Affected if Upload directory is within the webroot and serves files via the web server
-
Test for unrestricted .class uploadAttempt to upload a .class file through the upload feature, or inspect network requests to see if .class extensions are accepted without blocking.Affected if The system accepts .class file uploads without rejection or sanitization
If Interinfo DreamMaker is running with an exposed, unrestricted file upload function that accepts .class files into a web-accessible directory, the environment is vulnerable to remote code execution via CVE-2026-24729.
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 allowlist-based file type validation (both by extension and MIME type), verify file content/signatures, store uploads outside webroot, and disable script execution in upload directories.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24729 — 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-24729 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