Node TemplateDrupal extension · Node Template Project
CVE-2015-4397
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 Node Template module for Drupal allows remote attackers to hijack the authentication of users with the "access node template" permission for requests that delete node templates via unspecified vectors.
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 confidenceCSRF vulnerability in Drupal's Node Template module allows remote attackers to delete node templates by tricking authenticated users with the 'access node template' permission into visiting malicious pages. The attack exploits the lack of anti-CSRF tokens on delete operations.
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 TemplateDrupal 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 Node Template module is installedIn Drupal admin, go to Extend or Modules page and search for 'Node Template' or 'node_template' to confirm the module is installed and enabledAffected if The Node Template module is present and enabled on the Drupal site
-
Check if the 'access node template' permission is assignedGo to People > Permissions (or admin/config/people/permissions) and look for 'access node template' permission. Check which roles have this permission enabledAffected if Any authenticated role (except anonymous-only) has the 'access node template' permission granted
-
Confirm delete functionality exists in the moduleExamine the module directory (modules/node_template or similar path) and look for hook_menu or routing definitions that define delete callbacks for node templatesAffected if The module provides delete operations for node templates that could be triggered via CSRF
-
Identify users with the vulnerable permissionGo to People > Roles and for each role with 'access node template' permission, list the users assigned to that role to understand the exposure scopeAffected if Multiple users or high-privilege roles have the 'access node template' permission, increasing CSRF attack surface
If the Node Template module is installed and any authenticated user role has the 'access node template' permission, the site is affected by this CSRF vulnerability allowing unauthorized deletion of node templates.
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 CSRF tokens (form tokens) on all delete operations in the Node Template module, and consider adding a confirmation step for destructive actions. Users with this permission should avoid clicking untrusted links.
Fix this in Node Template
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-4397 — 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-4397 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