Spider ContactsDrupal extension · Spider Contacts Project
CVE-2015-4348
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 · uneditedSQL injection vulnerability in the Spider Contacts module for Drupal allows remote authenticated users with the "access Spider Contacts category administration" permission to execute arbitrary SQL commands 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 confidenceSQL injection vulnerability in the Spider Contacts module for Drupal allows remote authenticated users with the 'access Spider Contacts category administration' permission to execute arbitrary SQL commands via unspecified vectors in the module's category administration 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
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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:S/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 Spider Contacts module is installedIn Drupal admin, go to Extend or Modules page and search for 'Spider Contacts'. Check if the module is listed and enabled.Affected if The Spider Contacts module is installed and enabled on the Drupal site.
-
Confirm the module versionCheck the module's .info.yml file or the modules listing page for the version number. All versions of Spider Contacts are affected by this CVE.Affected if Any version of Spider Contacts is installed, as the vulnerability affects all versions.
-
Check for the vulnerable permission assignmentGo to Drupal admin: People > Permissions. Look for the permission 'access Spider Contacts category administration' and check which roles have it enabled.Affected if Any user role is granted the 'access Spider Contacts category administration' permission.
-
Identify users with the vulnerable permissionGo to Drupal admin: People > List. Review which users are assigned to roles that have the 'access Spider Contacts category administration' permission.Affected if Any authenticated or anonymous users have roles with this permission (beyond highly trusted administrators).
A user is affected if the Spider Contacts module is enabled and any role with the 'access Spider Contacts category administration' permission is assigned to users beyond highly trusted administrators.
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 dataUpdate the Spider Contacts module to the latest patched version. Until then, restrict the 'access Spider Contacts category administration' permission to only highly trusted administrative users and consider disabling the module if not required.
Fix this in Spider Contacts
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing2.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,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-4348 — 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-4348 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