Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-49342: CWE-352 Cross-Site Request Forgery (CSRF) in Wolfgang Häfelinger Custom Style

0
High
VulnerabilityCVE-2025-49342cvecve-2025-49342cwe-352
Published: Wed Dec 31 2025 (12/31/2025, 05:55:53 UTC)
Source: CVE Database V5
Vendor/Project: Wolfgang Häfelinger
Product: Custom Style

Description

Cross-Site Request Forgery (CSRF) vulnerability in Wolfgang Häfelinger Custom Style allows Stored XSS.This issue affects Custom Style: from n/a through 1.0.

AI-Powered Analysis

AILast updated: 01/07/2026, 12:57:41 UTC

Technical Analysis

CVE-2025-49342 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the Wolfgang Häfelinger Custom Style product, which leads to stored Cross-Site Scripting (XSS). CSRF vulnerabilities occur when an attacker tricks an authenticated user into submitting a malicious request to a web application without their consent. In this case, the CSRF flaw allows an attacker to inject malicious scripts that are stored persistently within the application, amplifying the impact by enabling subsequent execution of malicious code in the context of other users. The vulnerability affects all versions up to 1.0, with no specific version exclusions noted. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) indicates that the attack can be launched remotely over the network with low attack complexity, requires no privileges, but does require user interaction. The scope is changed, meaning the vulnerability affects components beyond the initially vulnerable component, increasing the risk. The impact includes partial loss of confidentiality, integrity, and availability due to the stored XSS payloads that can steal sensitive data, manipulate content, or disrupt service. No patches or known exploits are currently available, but the vulnerability is publicly disclosed and should be treated as a serious threat. The CWE-352 classification confirms the nature of the CSRF flaw. Given the stored XSS consequence, attackers can leverage this vulnerability for persistent attacks, including session hijacking, defacement, or malware distribution.

Potential Impact

For European organizations, this vulnerability poses a significant risk to web applications utilizing the Wolfgang Häfelinger Custom Style product. The stored XSS resulting from the CSRF attack can lead to unauthorized data access, session hijacking, and manipulation of web content, potentially compromising user data and organizational integrity. Confidentiality is at risk as attackers may steal sensitive information; integrity is threatened by unauthorized content changes; and availability may be impacted if attackers disrupt services or inject malicious scripts that degrade application functionality. Organizations in sectors such as finance, healthcare, and government, which handle sensitive personal and operational data, are particularly vulnerable. The ease of exploitation combined with the persistent nature of stored XSS increases the likelihood of targeted attacks. Additionally, the lack of available patches means organizations must rely on mitigation strategies to protect their environments. The reputational damage and regulatory consequences under GDPR for data breaches further elevate the impact for European entities.

Mitigation Recommendations

To mitigate CVE-2025-49342, European organizations should implement the following specific measures: 1) Employ anti-CSRF tokens in all state-changing requests to ensure that requests originate from legitimate users. 2) Implement strict Content Security Policy (CSP) headers to limit the execution of unauthorized scripts and reduce the impact of stored XSS. 3) Sanitize and validate all user inputs rigorously on both client and server sides to prevent injection of malicious scripts. 4) Use SameSite cookie attributes to restrict cross-origin requests and reduce CSRF attack vectors. 5) Monitor web application logs for unusual activities indicative of CSRF or XSS exploitation attempts. 6) Conduct regular security assessments and penetration testing focused on CSRF and XSS vulnerabilities. 7) Isolate or sandbox components that handle user-generated content to limit the scope of potential XSS attacks. 8) Engage with the vendor or community to track patch releases and apply updates promptly once available. 9) Educate users about phishing and social engineering tactics that may facilitate CSRF exploitation. These targeted actions go beyond generic advice and address the specific nature of this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-06-04T09:42:27.086Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6954bb9edb813ff03eca28b3

Added to database: 12/31/2025, 5:58:54 AM

Last enriched: 1/7/2026, 12:57:41 PM

Last updated: 1/8/2026, 7:21:30 AM

Views: 51

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats