dbcve.org
Commerce View ReceiptDrupal extension · Commerce View Receipt Project

CVE-2024-13257

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 1.0.3 or later.
See remediation →
62/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
Incorrect Authorization vulnerability in Drupal Commerce View Receipt allows Forceful Browsing.This issue affects Commerce View Receipt: from 0.0.0 before 1.0.3.

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 confidence

This is an incorrect authorization vulnerability in Drupal Commerce's View Receipt component that allows forceful browsing. Attackers can potentially access order receipt views without proper authentication or authorization by manipulating request parameters or URLs, exposing sensitive order information.

MitigationUpgrade Drupal Commerce View Receipt to version 1.0.3 or later, which should contain proper authorization checks to prevent unauthorized receipt 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
Commerce View ReceiptDrupal extension
Affected:< 1.0.3

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Commerce View Receipt module installation
    Locate the Commerce View Receipt module in your Drupal installation's modules directory or check via Drush: `drush pm-list --type=module --status=enabled | grep -i 'commerce.*view.*receipt'`
    Affected if The module is installed and enabled
  2. Determine installed module version
    Check the module's info.yml file (typically in modules/commerce_view_receipt/commerce_view_receipt.info.yml) or run `drush pm:list --format=json` to retrieve version metadata
    Affected if Version is below 1.0.3 (e.g., 1.0.2, 1.0.1, 1.0.0)
  3. Verify View Receipt routes are accessible
    Examine Drupal routing configuration for receipt-related routes (patterns like /order/{order}/receipt or /receipt/{receipt}) by inspecting the module's routing.yml file or using `drush router:list` to list routes
    Affected if Routes exist and are not restricted by explicit authorization requirements
  4. Test unauthenticated receipt access
    Attempt to access known receipt URLs (e.g., /order/[order_id]/receipt or /checkout/receipt/[order_id]) without authenticating or providing valid session credentials
    Affected if Receipt content is returned without requiring authentication or returning an access denied error

Your environment is affected if the Commerce View Receipt module is installed with a version lower than 1.0.3 and the receipt views are accessible without proper authorization checks.

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.

dbcve · scoped
Upgrade available Upgrade to 1.0.3 or later
Fixed in 1.0.3
Interim mitigation

Upgrade Drupal Commerce View Receipt to version 1.0.3 or later, which should contain proper authorization checks to prevent unauthorized receipt access.

Recommended fix High confidence

1.0.3

  1. Backup your Drupal site database and files before making any changes
  2. Update the Commerce View Receipt module to version 1.0.3 using Composer: 'composer update drupal/commerce_view_receipt --with-all-dependencies' or via the Drupal admin UI at /admin/modules
  3. Run database updates if any are required: 'drush updatedb' or via /admin/reports/status
  4. Clear the Drupal cache: 'drush cr' or via /admin/config/development/performance

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Commerce View Receipt Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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-2024-13257 — 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-2024-13257 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