CVE-2005-3767
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 · uneditedExponent CMS 0.96.3 and later versions does not properly restrict the types of uploaded files, which allows remote attackers to upload and execute PHP files.
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 confidenceExponent CMS 0.96.3 and later versions fails to properly validate file types during upload, permitting attackers to upload malicious PHP files that can be executed on the server for 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 data= 0.94= 0.95= 0.96.1= 0.96.3= 0.96.4CVSS 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
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 Exponent CMS installationLook for Exponent CMS files in the webroot (typically in /exponent, /cms, or at the root). Check for files like 'exp_version.php', 'index.php' with Exponent branding, or the 'exponent' directory structure.Affected if Exponent CMS files are found in the web directory
-
Confirm installed versionOpen the version file (commonly exp_version.php or version.php in the Exponent installation directory) and read the version number, or check the admin dashboard 'About' page.Affected if The version is 0.94, 0.95, 0.96.1, 0.96.3, or 0.96.4
-
Identify file upload functionalityNavigate to the file upload feature in the CMS (typically under Content > File Manager, or modules like 'file' or 'upload' in the administration panel). Confirm the upload form exists and is accessible.Affected if File upload module is present and accessible to users
-
Check file type validation configurationExamine the upload handling script (often in /modules/filedb/ or similar upload handling modules) for MIME type or extension validation logic. Look for whether a whitelist or blacklist approach is used, and whether PHP files are explicitly blocked.Affected if No strict allowlist-based file type validation is implemented, or PHP file extensions are not blocked
-
Verify upload directory locationCheck the configuration file (config.php or similar) for the upload path setting. Determine if uploaded files are stored within the webroot where they can be executed.Affected if Uploaded files are stored inside the web-accessible directory without script execution disabled
The environment is affected if Exponent CMS versions 0.94 through 0.96.4 are installed with an accessible file upload feature that lacks proper allowlist-based file type validation.
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 MIME type and extension), store uploads outside the webroot, and disable script execution in upload directories.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-3767 — 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-2005-3767 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