DrupalCMS
CVE-2015-3232
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 · uneditedOpen redirect vulnerability in the Field UI module in Drupal 7.x before 7.38 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the destinations parameter.
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 confidenceAn open redirect vulnerability exists in Drupal 7.x Field UI module before version 7.38. Attackers can craft malicious URLs using the destinations parameter to redirect authenticated users to arbitrary external websites, facilitating phishing attacks.
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
DrupalCMS
= 7.0= 7.1= 7.2= 7.3= 7.4= 7.5= 7.6= 7.7= 7.8= 7.9= 7.10= 7.11
Debian LinuxOperating system
= 7.0= 8.0CVSS 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
- None
AV:N/AC:M/Au:N/C:P/I:P/A:N
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.
-
Check installed Drupal core versionLocate the version number in the CHANGELOG.txt file in the Drupal root directory, or run 'drush status' and look for the Drupal version field, or check the 'system' table in the database for the 'version' entry.Affected if The installed version is any version before 7.38 (such as 7.0 through 7.37) and the site is using Drupal 7.x core.
-
Verify Field UI module is enabledCheck if the Field UI module is enabled by examining the 'system' table in the database where the name='field_ui' and status=1, or navigate to /admin/modules and look for Field UI in the list, or use drush pm-list --status=enabled --type=module.Affected if The Field UI module is currently enabled on the Drupal installation.
-
Inspect destination parameter handling in Field UIExamine the file modules/field_ui/field_ui.module and look for code that handles the 'destination' query parameter, specifically any drupal_goto() or redirect logic that uses the destination without proper validation.Affected if The code contains drupal_goto() or similar redirect calls that use the destination parameter without validating it is a local path.
-
Check Debian package version if using packaged DrupalIf running Debian Linux, run 'dpkg -l | grep drupal' or 'apt-cache policy drupal7' to check the installed Drupal package version.Affected if The installed drupal7 package version is earlier than the fixed version provided by Debian security updates.
A user is affected if their Drupal 7.x installation is running any version before 7.38 AND the Field UI module is enabled, allowing attackers to craft malicious URLs with the destination parameter to redirect authenticated users to external sites.
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 Drupal 7.x core to version 7.38 or later to apply the security patch that fixes the open redirect in the Field UI module.
Fix this in Drupal
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3232 — 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-3232 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