Spider ContactsDrupal extension · Spider Contacts Project
CVE-2015-4349
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 Spider Contacts module for Drupal allows remote attackers to hijack the authentication of administrators for requests that delete contact categories 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 · high confidenceCSRF vulnerability in the Spider Contacts Drupal module allows remote attackers to trick authenticated administrators into unknowingly deleting contact categories through maliciously crafted requests that the administrator's browser automatically submits due to lack of proper anti-CSRF tokens.
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
Spider ContactsDrupal 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
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:N/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.
-
Confirm Spider Contacts module installationIn Drupal admin, go to Modules page and search for 'Spider Contacts' in the list, or query the Drupal database: SELECT name, status FROM system WHERE name LIKE '%spider_contacts%';Affected if Module is present in the module list with status enabled (status = 1)
-
Identify module versionCheck the module's .info file in sites/all/modules/ or sites/all/modules/contrib/ for the version field, or query: SELECT info FROM system WHERE name LIKE '%spider_contacts%';Affected if Any version is returned - all versions of Spider Contacts are affected by CVE-2015-4349
-
Verify contact category deletion functionality existsNavigate to the Spider Contacts configuration page in Drupal admin (typically under Configuration > Webform > Spider Contacts or similar path) and confirm the ability to delete contact categories is presentAffected if Delete functionality for contact categories is accessible to authenticated administrators
-
Check for CSRF token implementation in deletion formsExamine the module's form code for delete operations - look in the module's .inc or .php files for form definitions that handle contact category deletion; verify if they include 'token' or 'form_token' elements for CSRF protectionAffected if No CSRF token validation is found in delete contact category form handlers
If the Spider Contacts Drupal module is installed and enabled, the site is affected since all versions lack proper anti-CSRF protection for contact category deletion operations.
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 dataApply available security updates for the Spider Contacts module; implement anti-CSRF form tokens for all state-changing operations (deletions, modifications) and validate the request origin server-side.
Fix this in Spider Contacts
Scoped from the published advisory
- Consultation3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-4349 — 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-4349 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