LiveActive security incident?Get immediate response
CVE Record

CVE-2021-37709: Insecure direct object reference of log files of the Import/Export feature

Shopware is an open source eCommerce platform. Versions prior to 6.4.3.1 contain a vulnerability involving an insecure direct object reference of log files of the Import/Export feature. Version 6.4.3.1 contains a patch. As workarounds for older versions of 6.1, 6.2, and 6.3, corresponding security measures are also available via a plugin.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Older Shopware 6 stores could expose Import/Export log files through an access-control weakness. An attacker with some authenticated access may be able to read sensitive log content. This is a confidentiality issue, not an integrity or outage issue, but logs can contain business or customer data.

Executive priority

Treat this as a near-term remediation item for Shopware stores because it can expose sensitive data, but the provided evidence does not support emergency active-exploitation handling. Prioritize systems with many admin users, delegated access, or sensitive Import/Export activity.

Technical view

CVE-2021-37709 affects Shopware platform versions through 6.4.3.0. The issue is described as an insecure direct object reference involving Import/Export feature log files, mapped to CWE-532. CVSS 3.1 is 6.5 with network access, low complexity, low privileges, no user interaction, and high confidentiality impact.

Likely exposure

Exposure is likely for Shopware platform deployments at or below 6.4.3.0, especially where Import/Export is used and log files retain sensitive data. CVSS indicates authentication is required, so anonymous internet exposure is not supported by the provided sources.

Exploitation context

The provided sources do not cite active exploitation, and the CVE is not marked KEV. The risk is unauthorized reading of Import/Export logs by a low-privileged authenticated user, which may expose confidential operational, customer, or commerce data if present in logs.

Researcher notes

The public record identifies the affected component and patch level but provides limited operational detail. Avoid assuming anonymous exploitability or specific data types in logs. Focus validation on version state, applied plugin workaround, user privileges, and whether logs contain regulated or business-sensitive information.

Mitigation direction

  • Upgrade Shopware platform to version 6.4.3.1 or later.
  • For older 6.1, 6.2, or 6.3 branches, apply Shopware's security plugin measures.
  • Review vendor advisory guidance before choosing a workaround path.
  • Limit low-privileged administrative access until the fix is confirmed.
  • Review Import/Export logs for sensitive retained data exposure.

Validation and detection

  • Inventory Shopware versions and flag all instances at or below 6.4.3.0.
  • Confirm the 6.4.3.1 patch or applicable security plugin is installed.
  • Identify who has access to the Import/Export feature and related logs.
  • Review retained Import/Export logs for confidential customer or business data.
  • Check security monitoring for unusual authenticated log access patterns.
Prepared
Confidence
high
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-532: 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-37709 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
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2021-37709Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
shopwareplatform<= 6.4.3.0Listed
Weakness

CWE details

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

CWE-532 · source CWE mapping

Insertion of Sensitive Information into Log File

Insertion of Sensitive Information into Log File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.