CVE-2012-6643
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 · uneditedMultiple SQL injection vulnerabilities in the update_counter function in includes/functions.php in ClipBucket 2.6 allow remote attackers to execute arbitrary SQL commands via the time parameter to (1) videos.php or (2) channels.php. NOTE: some of these details are obtained from third party information.
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 confidenceSQL injection vulnerability in ClipBucket 2.6's update_counter function in includes/functions.php allows remote attackers to execute arbitrary SQL commands via the 'time' parameter in videos.php and channels.php.
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= 2.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
- 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 ClipBucket installationLocate the ClipBucket installation directory and check for the existence of includes/functions.php, videos.php, and channels.php filesAffected if The application files exist and the vulnerable code paths are present
-
Confirm ClipBucket versionCheck the version file or header in ClipBucket (typically in an index.php, version.php, or admin dashboard) to determine if the installed version is 2.6Affected if The installed version is exactly 2.6 (the only affected version per the CVE)
-
Inspect update_counter functionOpen includes/functions.php and locate the update_counter function definition. Examine how the 'time' parameter is handled in SQL queries within this functionAffected if The function directly uses the 'time' parameter in SQL queries without apparent sanitization or parameterization
-
Check parameter exposure in videos.phpOpen videos.php and search for code that passes a 'time' parameter to the update_counter function. Determine if this parameter originates from user input (GET/POST request)Affected if videos.php passes unsanitized user-supplied 'time' parameter to update_counter
-
Check parameter exposure in channels.phpOpen channels.php and search for code that passes a 'time' parameter to the update_counter function. Determine if this parameter originates from user inputAffected if channels.php passes unsanitized user-supplied 'time' parameter to update_counter
The environment is affected if ClipBucket version 2.6 is installed and the update_counter function in includes/functions.php accepts and uses the 'time' parameter from videos.php or channels.php without proper SQL injection protection.
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 dataFix the update_counter function to use parameterized queries or proper input sanitization for the time parameter before executing SQL statements.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-6643 — 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-2012-6643 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