dbcve.org
ClipbucketApplication · Clip Bucket

CVE-2016-1000307

MEDIUM · 6.1 CVSS v3.0 Published 2017-04-06
Fix available
A fix is available. Upgrade to after 2.8.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Multiple Cross Site Scripting (XSS) Vulnerabilities in ClipBucket v2.8.1 and probably prior allow Remote Attackers to inject arbitrary web script or HTML via (1) profile_desc, about_me, schools, occupation, companies, hobbies, fav_movies, fav_music, fav_books parameters to ProfileSettings page; (2) note parameter to PersonalNotes Section; (3) closed_msg, description, allowed_types parameters to WebsiteConfigurations Section. NOTE: the collection_description vector is already covered by CVE-2015-4673.

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 confidence

Multiple stored XSS vulnerabilities in ClipBucket v2.8.1 allow remote attackers to inject arbitrary JavaScript/HTML via unsanitized user input in profile settings (profile_desc, about_me, schools, occupation, companies, hobbies, fav_movies, fav_music, fav_books), personal notes (note), and website configuration parameters (closed_msg, description, allowed_types).

MitigationImplement proper input validation and output encoding across all identified parameters. Use context-appropriate escaping (HTML entity encoding for displayed text) and consider Content Security Policy headers to mitigate XSS impact.

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
ClipbucketApplication
Affected:<= 2.8.1

CVSS 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
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ClipBucket installation and version
    Check the version.php file or admin dashboard for the ClipBucket version number. Common locations include /upload/includes/functions.php or the admin panel 'System Info' section.
    Affected if The installed version is ClipBucket 2.8.1 or lower.
  2. Verify user profile functionality is enabled
    Log in as a registered user and navigate to profile editing settings. Look for profile fields such as 'About Me', 'Profile Description', 'Schools', 'Occupation', 'Companies', 'Hobbies', 'Favorite Movies', 'Favorite Music', or 'Favorite Books'.
    Affected if User profile editing features are active and these fields are accessible for input.
  3. Test profile fields for XSS vulnerability
    In the profile editing section, inject a test payload like <script>alert('XSS')</script> into one or more of the affected profile fields (profile_desc, about_me, schools, occupation, companies, hobbies, fav_movies, fav_music, fav_books). Save the profile and view the page to see if the script executes.
    Affected if The injected JavaScript/HTML is rendered unescaped when the profile is displayed.
  4. Verify personal notes feature is accessible
    Check if the 'Personal Notes' or 'Note' feature is available in the user dashboard or profile section.
    Affected if The personal notes feature is enabled and accessible to users.
  5. Test website configuration parameters for XSS
    Access the admin control panel, navigate to website settings or configuration. Look for fields labeled 'Closed Message', 'Description', or 'Allowed Types'. Inject an XSS test payload into these fields and save the configuration.
    Affected if The configuration fields accept and display unsanitized HTML/JavaScript input.

A user is affected if they have ClipBucket version 2.8.1 or lower installed with user profile features or admin configuration panels accessible, where the listed input fields render injected script tags without encoding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.8.1
Interim mitigation

Implement proper input validation and output encoding across all identified parameters. Use context-appropriate escaping (HTML entity encoding for displayed text) and consider Content Security Policy headers to mitigate XSS impact.

Fix this in Clipbucket Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1000307 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-1000307 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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