LiveActive security incident?Get immediate response
CVE Record

CVE-2021-25962: Shuup - Formula Injection in Checkout Addresses

“Shuup” application in versions 0.4.2 to 2.10.8 is affected by the “Formula Injection” vulnerability. A customer can inject payloads in the name input field in the billing address while buying a product. When a store administrator accesses the reports page to export the data as an Excel file and opens it, the payload gets executed.

HighCVSS 8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A customer could place spreadsheet formula content in a Shuup checkout billing-name field. If an administrator later exports report data to Excel and opens it, the spreadsheet application may execute that content. The risk is indirect but business-relevant because customer input can cross into an admin workstation through normal reporting.

Executive priority

Prioritize remediation for internet-facing commerce sites where staff routinely export reports. This is not described as actively exploited in the provided sources, but it creates a credible path from customer input to administrator workstation compromise.

Technical view

CVE-2021-25962 is a CWE-1236 formula injection issue in Shuup versions 0.4.2 through 2.10.8. The reported path is billing address name input during purchase, followed by administrator report export to an Excel file. CVSS 3.1 is 8.0 high, with low attack complexity, low privileges, and required user interaction.

Likely exposure

Exposure is most likely for organizations running Shuup 0.4.2 to 2.10.8 that allow customer checkout accounts and have administrators exporting order or report data to Excel-compatible spreadsheets.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires a customer-level input opportunity and an administrator opening the exported spreadsheet, so the practical risk depends on reporting workflows and endpoint controls.

Researcher notes

Evidence is limited to the CVE description, CVSS data, CWE-1236 classification, affected range, and a referenced Shuup commit. The bundle does not name a fixed release, operational workaround, or exploitation in the wild.

Mitigation direction

  • Identify whether Shuup is deployed and confirm its version.
  • Review Shuup vendor guidance and the referenced commit before selecting a fixed version.
  • Upgrade or backport the vendor fix if running affected versions.
  • Restrict report exports and spreadsheet opening to trusted administrative workflows until remediated.
  • Treat exported spreadsheets containing customer input as untrusted files.

Validation and detection

  • Inventory Shuup instances and compare versions against 0.4.2 through 2.10.8.
  • Confirm whether checkout billing names appear in administrator Excel report exports.
  • In a non-production environment, verify formula-like input is exported as plain text.
  • Check that administrative reporting workflows no longer expose raw customer-controlled spreadsheet cells.
  • Document compensating controls if upgrade timing is delayed.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1236: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-25962 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H2.15.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8High
CVSS 3.1 vector shape for CVE-2021-25962Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
shuupshuup0.4.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1236 · source CWE mapping

Improper Neutralization of Formula Elements in a CSV File

Improper Neutralization of Formula Elements in a CSV File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.