VulnerabilityPublished 5 Aug 2025Updated 7 Aug 2025

CVE-2025-51541: Cross-site Scripting

Source CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

6.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Immediate mitigation should include restricting access to the /recovery/install/database-configuration/ endpoint to trusted administrators only, ideally via network-level controls such as VPNs or IP whitelisting. 2. Implement strict input validation and output encoding on the c_database_schema field to ensure all user-supplied data is properly sanitized before rendering. 3. Add robust CSRF protections on all POST requests in the installation interface, such as synchronizer tokens or double-submit cookies, to prevent unauthorized request forgery. 4. Monitor web server logs for suspicious POST requests to the vulnerable endpoint and unusual user activity during installation phases. 5. Educate administrators and developers about the risks of visiting untrusted web pages while logged into or accessing the Shopware installation interface. 6. Apply security headers such as Content Security Policy (CSP) to limit the execution of unauthorized scripts. 7. Once available, promptly apply official patches or updates from Shopware addressing this vulnerability. 8. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block XSS payloads targeting this endpoint. 9. Conduct security audits and penetration testing focusing on installation and configuration interfaces to identify similar weaknesses.

Description

A stored cross-site scripting (XSS) vulnerability exists in the Shopware 6 installation interface at /recovery/install/database-configuration/. The c_database_schema field fails to properly sanitize user-supplied input before rendering it in the browser, allowing an attacker to inject malicious JavaScript. This vulnerability can be exploited via a Cross-Site Request Forgery (CSRF) attack due to the absence of CSRF protections on the POST request. An unauthenticated remote attacker can craft a malicious web page that, when visited by a victim, stores the payload persistently in the installation configuration. As a result, the payload executes whenever any user subsequently accesses the vulnerable installation page, leading to persistent client-side code execution.

Impact

For European organizations using Shopware 6, particularly those in early installation or configuration phases, this vulnerability poses a significant risk. Since the vulnerability is exploitable without authentication and via CSRF, attackers can target administrators or developers who access the installation interface, injecting persistent malicious scripts. This can lead to theft of sensitive configuration data, session tokens, or credentials, potentially compromising the entire e-commerce platform. The persistent nature of the XSS means that multiple users can be affected over time, increasing the attack surface. Given the widespread adoption of Shopware in European e-commerce markets, especially in Germany and neighboring countries, the risk of exploitation could lead to data breaches, reputational damage, and financial losses. Additionally, attackers might leverage this vulnerability as a foothold to pivot into internal networks or escalate privileges. The absence of CSRF protections exacerbates the risk, making it easier for attackers to exploit the vulnerability remotely without direct interaction with the Shopware system beyond victim user interaction. Although availability is not impacted, the confidentiality and integrity breaches can disrupt business operations and customer trust.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 13 Aug 2025, 01:01 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats