The Extensible Catalog Drupal ToolkitDrupal extension · The Extensible Catalog Drupal Toolkit Project
CVE-2015-5508
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 · uneditedCross-site request forgery (CSRF) vulnerability in the XC NCIP Provider module in the eXtensible Catalog (XC) Drupal Toolkit allows remote attackers to hijack the authentication of users with the "administer ncip providers" permission for requests that alter NCIP providers via a crafted request.
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 confidenceCross-site request forgery (CSRF) vulnerability in the XC NCIP Provider module of the eXtensible Catalog Drupal Toolkit allows remote attackers to hijack the authentication of users who possess the 'administer ncip providers' permission. Attackers can craft malicious requests that, when triggered by an authenticated administrator, will alter NCIP provider configurations without the victim's consent.
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
The Extensible Catalog Drupal ToolkitDrupal extension
all versionsCVSS 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
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:H/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.
-
Identify if the eXtensible Catalog Drupal Toolkit is installedLocate the Drupal installation directory and check for the presence of the 'extensible_catalog' or 'xc' directory in modules or sites/all/modulesAffected if The eXtensible Catalog Drupal Toolkit is found in the Drupal installation
-
Check if the XC NCIP Provider module is enabledIn the Drupal admin interface, navigate to Administration > Modules (or use drush pm-list) and look for 'XC NCIP Provider' or 'NCIP Provider' module in the listAffected if The NCIP Provider module is installed and enabled in Drupal
-
Verify if any user role has the 'administer ncip providers' permissionNavigate to Administration > People > Permissions (or admin/people/permissions) and search for 'administer ncip providers' - check which roles have this permission enabledAffected if Any authenticated user role (including administrator) has the 'administer ncip providers' permission granted
-
Inspect NCIP provider configuration forms for missing CSRF protectionNavigate to the NCIP Provider settings page (typically under Administration > Configuration > Library > NCIP Providers or similar path) and examine the HTML source of forms that modify provider settings for the presence of form tokens or nonce fieldsAffected if Forms for modifying NCIP provider settings lack anti-CSRF tokens (form_token, nonce, or similar security tokens in the form markup)
A user is affected if the XC NCIP Provider module is enabled and any user role possesses the 'administer ncip providers' permission, since the module lacks CSRF protection on its configuration forms.
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 dataImplement anti-CSRF tokens (form tokens) on all forms that modify NCIP provider settings to validate request authenticity, and validate the Referer header or Origin header on POST requests.
Fix this in The Extensible Catalog Drupal Toolkit
Scoped from the published advisory
- Consultation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5508 — 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-2015-5508 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