CVE-2002-0718
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 · uneditedWeb authoring command in Microsoft Content Management Server (MCMS) 2001 allows attackers to authenticate and upload executable content, by modifying the upload location, aka "Program Execution via MCMS Authoring Function."
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 confidenceMicrosoft Content Management Server (MCMS) 2001 contains a vulnerability in its web authoring function that allows authenticated users to upload executable content by modifying the upload location parameter. This enables remote attackers to potentially execute arbitrary code on the server by uploading malicious executable files to accessible locations.
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 data= 2001CVSS 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 MCMS 2001 installationCheck for Microsoft Content Management Server 2001 installation by looking in Program Files\Microsoft Content Management Server or checking registry key HKLM\SOFTWARE\Microsoft\CMS for the installed versionAffected if MCMS 2001 is installed on the server
-
Confirm web authoring service is enabledCheck the MCMS Server Administration site, specifically the 'Authoring' settings under Site Manager, or inspect the web.config file in the MCMS web authoring application directory for enabled authoring featuresAffected if Web authoring functionality is enabled and accessible to users
-
Identify upload mechanism configurationLocate the file upload handling component in the MCMS web authoring application (typically under the 'Authoring' or 'PostAuthoring' virtual directories) and inspect the upload handler configuration for path and file type validation settingsAffected if Upload handling allows unrestricted file type selection or permits path modification
-
Check web-accessible directories for suspicious filesSearch web root directories (especially /NR/ and /Authoring/ paths) for executable files (.asp, .aspx, .exe, .dll, .com) that were uploaded after the MCMS installation date, or files with double extensionsAffected if Unexpected executable files exist in web-accessible MCMS directories
-
Review user permissions for authoring functionExamine the MCMS User Manager to see which users or groups have 'Author' or 'Admin' level access to the web authoring feature, and check for any unauthorized accounts added to these rolesAffected if Untrusted or unexpected users have authoring permissions enabled
The environment is affected if MCMS 2001 is installed and the web authoring function is enabled, allowing authenticated users to potentially upload and execute malicious files.
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 dataDisable or restrict the web authoring function to only trusted users, implement strict file type validation and path restrictions on upload mechanisms, and apply any available Microsoft security patches for MCMS 2001.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0718 — 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-2002-0718 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