CVE-2007-2214
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 file upload vulnerability in includes/upload_file.php in DmCMS allows remote attackers to upload arbitrary PHP scripts by placing a script's contents in both the File2 and File3 parameters, and sending a ok.php?do=act Referer.
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 confidenceUnrestricted file upload vulnerability in DmCMS allows remote attackers to bypass file upload restrictions by placing PHP script content in File2 and File3 parameters and sending requests to ok.php?do=act, potentially achieving remote code execution.
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 dataall versionsCVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Verify DmCMS installationCheck if the DmCMS application directory exists on the web server. Common paths include /dmcms/, /cms/, or similar. Search for files named ok.php in the web root.Affected if DmCMS is present on the server and ok.php exists in the web-accessible directory.
-
Identify the vulnerable upload endpointLocate ok.php and verify it accepts the 'do' parameter set to 'act'. Inspect the source code to confirm File2 and File3 parameters are processed for file uploads.Affected if ok.php?do=act handles File2 or File3 parameters for upload functionality.
-
Confirm upload functionality is accessibleAttempt to access ok.php?do=act directly through a web request or review server access logs for requests to this endpoint.Affected if The upload endpoint is accessible without authentication or proper access controls.
-
Check file type validationReview the upload handling code in ok.php to determine if file extension or MIME type validation exists for File2 and File3 parameters.Affected if No server-side validation of file extensions or MIME types is performed on uploaded files.
-
Determine upload storage locationIdentify where uploaded files are stored by examining the ok.php code. Check if files are saved in a web-accessible directory with their original filenames.Affected if Uploaded files are stored within the web root and retain their original filenames, allowing direct access and execution.
If DmCMS is installed with the ok.php?do=act endpoint accessible and no server-side file type validation exists, the system is affected by this unrestricted file upload vulnerability.
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 for uploaded files, verify file extensions and MIME types server-side, store uploads outside the web root or rename files to prevent execution, and remove the vulnerable upload_file.php endpoint or properly restrict access.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2214 — 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-2007-2214 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