Custom SitemapDrupal extension · Osscube
CVE-2015-4353
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 Custom Sitemap module for Drupal allows remote attackers to hijack the authentication of administrators for requests that delete sitemaps 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 confidenceThis is a Cross-Site Request Forgery (CSRF) vulnerability in the Custom Sitemap module for Drupal. The vulnerability allows remote attackers to trick authenticated administrators into unknowingly executing delete operations on sitemaps. Since the module fails to validate anti-CSRF tokens on delete requests, an attacker can craft a malicious page that forces an admin's browser to send authenticated delete requests.
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
Custom SitemapDrupal 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 Custom Sitemap module is installedNavigate to Drupal admin panel and check the list of installed modules, or inspect the modules directory for a custom_sitemap or sitemap-related custom module.Affected if The Custom Sitemap module by Osscube is present in the Drupal modules directory or module list.
-
Confirm the module handles sitemap deletionSearch the module's PHP files for delete-related functions, form submissions, or menu callbacks that handle sitemap deletion (look for 'delete', 'remove', or hook_menu paths ending in '/delete').Affected if The module contains code that processes delete operations for sitemaps without requiring explicit user confirmation beyond a standard form submission.
-
Inspect delete form code for CSRF token validationOpen the PHP file containing the delete form or menu callback. Look for the presence of Form API token validation using form_validate or form_submit functions, specifically check for token validation logic using drupal_valid_token or similar functions.Affected if The delete operation code does NOT include drupal_valid_token() or '#token' => TRUE in the form build array, meaning anti-CSRF tokens are not being validated.
-
Check module permissions configurationExamine the module's hook_permission implementation to confirm delete operations are restricted to authenticated administrators only.Affected if Delete operations are accessible to users with administrator roles without additional CSRF protection.
The environment is affected if the Osscube Custom Sitemap module is installed and its delete operations lack CSRF token validation in the form code.
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 dataEnable Drupal's built-in CSRF token validation (Form API tokens) on all sitemap delete operations in the module. Additionally, administrators should avoid browsing untrusted sites while authenticated to the Drupal admin panel.
Fix this in Custom Sitemap
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-4353 — 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-4353 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