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-65591: n/a

0
Medium
VulnerabilityCVE-2025-65591cvecve-2025-65591
Published: Tue Dec 16 2025 (12/16/2025, 00:00:00 UTC)
Source: CVE Database V5

Description

CVE-2025-65591 is a medium severity Cross Site Scripting (XSS) vulnerability affecting nopCommerce version 4. 90. 0 via its Currencies functionality. The vulnerability allows an authenticated user with low privileges to inject malicious scripts that can execute in the context of other users, potentially leading to data theft or session hijacking. Exploitation requires user interaction and privileges, but no known exploits are currently reported in the wild. The vulnerability impacts confidentiality and integrity but not availability. European organizations using nopCommerce 4. 90. 0 for e-commerce operations should prioritize patching or mitigating this issue to prevent targeted attacks. Countries with significant e-commerce sectors and nopCommerce adoption, such as Germany, the UK, France, and the Netherlands, are most likely to be affected.

AI-Powered Analysis

AILast updated: 12/23/2025, 19:34:02 UTC

Technical Analysis

CVE-2025-65591 identifies a Cross Site Scripting (XSS) vulnerability in nopCommerce version 4.90.0, specifically within the Currencies functionality. XSS vulnerabilities occur when an application does not properly sanitize user-supplied input, allowing attackers to inject malicious scripts that execute in other users' browsers. In this case, the vulnerability requires an attacker to have low-level privileges (PR:L) and user interaction (UI:R), meaning the attacker must be authenticated and trick a user into triggering the malicious payload. The CVSS vector indicates network attack vector (AV:N), low attack complexity (AC:L), and a scope change (S:C), meaning the vulnerability can affect resources beyond the initially vulnerable component. The impact affects confidentiality and integrity to a limited extent (C:L/I:L), but does not affect availability (A:N). While no known exploits are currently in the wild, the vulnerability poses a risk to e-commerce platforms using nopCommerce 4.90.0, as attackers could steal session tokens, manipulate user data, or perform actions on behalf of other users. The absence of a patch link suggests that a fix may not yet be publicly available, emphasizing the need for immediate mitigation strategies. The CWE-79 classification confirms this is a classic reflected or stored XSS issue. Organizations should review their input validation and output encoding practices in the Currencies module and consider deploying web application firewalls (WAFs) to detect and block malicious payloads.

Potential Impact

For European organizations, especially those operating e-commerce websites using nopCommerce 4.90.0, this vulnerability can lead to unauthorized access to user sessions, theft of sensitive information such as payment details, and potential manipulation of currency settings that could affect transaction integrity. The confidentiality and integrity of customer data are at risk, which could result in reputational damage, regulatory penalties under GDPR, and financial losses. Since the vulnerability requires authentication and user interaction, insider threats or social engineering attacks could be leveraged to exploit it. The lack of availability impact means service disruption is unlikely, but the compromise of user trust and data security remains significant. Given the widespread use of nopCommerce in European SMEs and online retailers, the threat could affect a broad range of sectors including retail, finance, and hospitality.

Mitigation Recommendations

1. Monitor official nopCommerce channels for patches addressing CVE-2025-65591 and apply them promptly once released. 2. Implement strict input validation and output encoding in the Currencies functionality to sanitize user inputs and prevent script injection. 3. Deploy Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 4. Use Web Application Firewalls (WAFs) configured to detect and block common XSS attack patterns targeting the affected module. 5. Conduct security awareness training to reduce the risk of social engineering attacks that could facilitate exploitation. 6. Review user privilege assignments to minimize the number of users with access to currency management features. 7. Perform regular security testing, including automated scanning and manual code reviews, focusing on input handling in the affected components.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-11-18T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 6941a4041a61eff6269a933a

Added to database: 12/16/2025, 6:25:08 PM

Last enriched: 12/23/2025, 7:34:02 PM

Last updated: 2/7/2026, 9:21:32 AM

Views: 36

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