Web Dorado Spider Video PlayerDrupal extension · Web Dorado
CVE-2015-4352
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 Video Player module for Drupal allows remote attackers to hijack the authentication of administrators for requests that delete videos 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 confidenceCross-site request forgery (CSRF) vulnerability in the Spider Video Player Drupal module allows remote attackers to delete videos by tricking authenticated administrators into visiting malicious pages. The attack exploits the lack of anti-CSRF tokens on video deletion functionality, enabling attackers to perform actions with administrator privileges without direct access.
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
Web Dorado Spider Video PlayerDrupal 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.
-
Verify Spider Video Player module is installedAccess Drupal administration panel and navigate to Modules, or check the Drupal modules directory for 'spider_video_player' folderAffected if The spider_video_player module folder exists in the Drupal modules directory or appears in the modules list
-
Confirm the module is enabledCheck if Spider Video Player is listed as enabled in Drupal's module administration pageAffected if The module is enabled and active in the Drupal installation
-
Check module version informationLook for a version.php or .info file within the spider_video_player module directory, or check the module's description page in Drupal adminAffected if Any version of Spider Video Player is installed (all versions are affected)
-
Verify video management functionality existsAccess the Spider Video Player admin interface and confirm video management options including deletion are presentAffected if Video deletion functionality is accessible through the admin interface
If the Spider Video Player module is installed and enabled in Drupal, the environment is affected by CVE-2015-4351 since all versions lack anti-CSRF protection on video 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 dataUpgrade to a patched version of the Spider Video Player module if available, or implement anti-CSRF tokens (form tokens) on all video management forms including deletion operations. Alternatively, disable the module until a fix is available.
Fix this in Web Dorado Spider Video Player
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-4352 — 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-4352 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