Node CloneApplication · Drupal
CVE-2008-4633
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 · uneditedSQL injection vulnerability in Node Vote 5.x before 5.x-1.1 and 6.x before 6.x-1.0, a module for Drupal, when "Allow user to vote again" is enabled, allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors related to a "previously cast vote."
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 confidenceSQL injection vulnerability in Drupal's Node Vote module allows remote authenticated users to execute arbitrary SQL commands when the 'Allow user to vote again' setting is enabled. The vulnerability stems from improper handling of previously cast vote data in SQL queries.
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
Node CloneApplication
= 4.7.x-1.0= 4.7.x-1.1= 4.7.x-1.2= 4.7.x-1.3= 4.7.x-2.1= 5= 6CVSS 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
- M
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Verify Node Vote module is installedCheck the Drupal modules directory for the nodevote folder, or query the system table: SELECT * FROM system WHERE name = 'nodevote' AND type = 'module';Affected if No rows returned means the module is not installed and the user is not affected.
-
Determine the installed Node Vote module versionQuery the system table: SELECT version, info FROM system WHERE name = 'nodevote' AND type = 'module'; The info column often contains a version array. Alternatively, inspect the nodevote.module or nodevote.info file directly.Affected if Version falls within 4.7.x-1.0 through 4.7.x-2.1, or is 5.x or 6.x (all versions prior to 5.x-1.1 or 6.x-1.0).
-
Check if the voting feature is in useExamine the nodevote configuration table or module settings. Query: SELECT * FROM variable WHERE name LIKE '%nodevote%'; Inspect the Drupal variable table for vote-related settings.Affected if No vote-related configuration exists, meaning the voting functionality has never been configured or enabled.
-
Verify the 'Allow user to vote again' settingCheck the Drupal variables table for the nodevote_recast_vote setting: SELECT * FROM variable WHERE name = 'nodevote_recast_vote'; Or inspect the module's administrative settings page in Drupal.Affected if The variable nodevote_recast_vote is set to a non-zero value (enabled). This is the required condition for exploitation.
A user is affected only if they have Node Vote module installed with a version prior to 5.x-1.1 or 6.x-1.0 AND the 'Allow user to vote again' setting is enabled.
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 Node Vote module to version 5.x-1.1 or 6.x-1.0 or later to obtain patched code. Alternatively, disable the 'Allow user to vote again' setting if upgrading is not feasible.
Fix this in Node Clone
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-4633 — 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-4633 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