dbcve.org
CtoolsDrupal extension · Chaos Tool Suite Project

CVE-2015-7875

HIGH · 7.5 CVSS v3.0 Published 2017-08-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
ctools 6.x-1.x before 6.x-1.14 and 7.x-1.x before 7.x-1.8 in Drupal does not verify the "edit" permission for the "content type" plugins that are used on Panels and similar systems to place content and functionality on a page.

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 confidence

The ctools module (Chaos Tools Suite) for Drupal 6.x and 7.x contains an access control bypass vulnerability where content type plugins used by Panels and similar systems fail to verify the user's 'edit' permission before allowing content modifications. This allows authenticated users to potentially modify content they should not have permission to edit.

MitigationUpdate ctools to version 6.x-1.14 or 7.x-1.8 or later to include proper permission verification for content type plugins. If immediate patching is not possible, review user roles and permissions for Panels-related functionality.

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
CtoolsDrupal extension
Affected:= 6.x-1.0= 6.x-1.1= 6.x-1.2= 6.x-1.3= 6.x-1.4= 6.x-1.5= 6.x-1.6= 6.x-1.7= 6.x-1.8= 6.x-1.9= 6.x-1.11= 6.x-1.12

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
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Check installed ctools version
    Navigate to Drupal admin: Site Build > Modules (or /admin/build/modules). Locate the 'Chaos Tools Suite' or 'Ctools' module and note the version displayed. Alternatively, check the ctools.info file in the module directory for the 'version' line.
    Affected if The version is any of: 6.x-1.0, 6.x-1.1, 6.x-1.2, 6.x-1.3, 6.x-1.4, 6.x-1.5, 6.x-1.6, 6.x-1.7, 6.x-1.8, 6.x-1.9, 6.x-1.11, or 6.x-1.12.
  2. Confirm Panels module is enabled
    In Drupal admin at /admin/build/modules, verify that the 'Panels' module (or 'Panels Advanced Panels' or similar) is enabled. Check if any Panel pages or mini panels exist at /admin/build/pages.
    Affected if Panels module is enabled and Panel pages or content type plugins are in use.
  3. Verify content type plugin usage
    Check the Panels configuration at /admin/build/pages. Look for any enabled panel pages that use content type plugins (as opposed to custom content or other node-based plugins).
    Affected if Panel pages using content type plugins are configured and visible on the site.

If the ctools module version is between 6.x-1.0 and 6.x-1.12 (inclusive) and Panels or similar systems using content type plugins are enabled and in use, the site is affected by this access control bypass.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update ctools to version 6.x-1.14 or 7.x-1.8 or later to include proper permission verification for content type plugins. If immediate patching is not possible, review user roles and permissions for Panels-related functionality.

Fix this in Ctools Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-7875 — 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-2015-7875 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