dbcve.org
CommerceDrupal extension · Commerceguys

CVE-2014-9025

MEDIUM · 5.0 CVSS v2.0 Published 2014-11-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The default checkout completion rule in the commerce_order module in the Drupal Commerce module 7.x-1.x before 7.x-1.10 for Drupal uses the email address as the username for new accounts created at checkout, which allows remote attackers to obtain sensitive information 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 confidence

The Drupal Commerce module 7.x-1.x before 7.x-1.10 has a default checkout completion rule that uses the customer's email address as the username for newly created accounts. This exposes email addresses as valid usernames, allowing attackers to confirm which email addresses are registered on the site and potentially use them for credential stuffing or phishing attacks.

MitigationUpgrade to Drupal Commerce 7.x-1.10 or later, and modify the checkout completion rule to generate anonymous usernames instead of using the email address.

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
CommerceDrupal extension
Affected:= 7.x-1.0= 7.x-1.1

CVSS 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
Low
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Drupal Commerce version
    In the Drupal admin interface, navigate to Modules or use Drush command 'drush pm-list --type=module --status=enabled | grep commerce' to list the Commerce module version. Alternatively, check the commerce.info file in the modules directory for the version string.
    Affected if The installed version is 7.x-1.0 or 7.x-1.1, or any 7.x-1.x version prior to 7.x-1.10.
  2. Locate the checkout completion rule configuration
    Navigate to Drupal admin: Configuration > Workflow > Rules (or equivalent path /admin/config/workflow/rules). Look for a rule named 'Checkout completion' or similar that triggers upon order completion.
    Affected if A checkout completion rule exists and is enabled.
  3. Inspect the rule action that creates user accounts
    Edit the checkout completion rule and examine the actions. Look for an action that creates a new user account or registers a new user.
    Affected if The rule contains an action to create a new user account.
  4. Verify if the email address is used as the username
    In the user creation action within the rule, examine the 'Username' or 'Name' field mapping. Check if it references the customer's email address field (e.g., order:mail or commerce-order:mail).
    Affected if The username field is mapped directly to the customer's email address.
  5. Test email address enumeration vulnerability
    Attempt to complete a checkout as a new customer with an arbitrary email address. If the site reveals that the email is already registered or allows username enumeration, the vulnerability is present.
    Affected if The system confirms whether an email address is already registered on the site.

A user is affected if Drupal Commerce 7.x-1.x versions prior to 7.x-1.10 are installed AND the default checkout completion rule is enabled with email-based usernames.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Drupal Commerce 7.x-1.10 or later, and modify the checkout completion rule to generate anonymous usernames instead of using the email address.

Fix this in Commerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-9025 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-9025 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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