DrupalCMS
CVE-2008-3742
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 the BlogAPI module in Drupal 5.x before 5.10 and 6.x before 6.4 allows remote authenticated users to execute arbitrary code by uploading a file with an executable extension, which is not validated.
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 confidenceThe BlogAPI module in Drupal 5.x before 5.10 and 6.x before 6.4 contains an unrestricted file upload vulnerability. Authenticated users can upload files with executable extensions (e.g., .php, .exe) without proper validation, allowing them to execute arbitrary code on the server.
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
DrupalCMS
= 5.0= 5.1= 5.2= 5.3= 5.4= 5.5= 5.6= 5.7= 5.8= 5.9= 6.0= 6.1CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/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.
-
Determine Drupal core versionCheck the CHANGELOG.txt file in the Drupal root directory, or query the system table in the database for the version record, or look at the VERSION constant in includes/bootstrap.incAffected if The installed version is 5.0 through 5.9, or 6.0 through 6.1 (versions before 5.10 or 6.4)
-
Verify BlogAPI module is enabledCheck the system table in the database for modules with name='blogapi' and status=1, or inspect the modules directory for blogapi.module fileAffected if The BlogAPI module is installed and enabled
-
Confirm BlogAPI file upload feature is accessibleCheck if the BlogAPI module exposes file upload functionality - look for blogapi_upload or xmlrpc endpoint that accepts file uploadsAffected if Authenticated users can access the BlogAPI file upload functionality
-
Check uploaded files directory is web-accessibleInspect the sites/default/files directory or custom upload path configured for BlogAPI to confirm files are stored in a web-accessible locationAffected if Uploaded files are stored in a directory accessible via HTTP
A user is affected if they run Drupal versions 5.0-5.9 or 6.0-6.1 with the BlogAPI module enabled and its file upload feature accessible to authenticated users, with uploaded files stored in a web-accessible directory.
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 dataUpgrade Drupal to version 5.10 or 6.4 or later. Additionally, implement strict file extension validation and whitelist allowed file types in the BlogAPI module's file upload handler.
Fix this in Drupal
Scoped from the published advisory
- 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-2008-3742 — 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-2008-3742 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