CVE-2025-65589: nopcommerce · Cross-site Scripting
Affects nopcommerceSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% 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:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Dec 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
NuGetnopcommerce/nopcommercepkg:nuget/nopcommerce/nopcommerceOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-65589, organizations should first verify if they are running nopCommerce version 4.90.0 and plan immediate upgrades once an official patch is released. In the absence of a patch, implement strict input validation on all attribute fields to reject or sanitize potentially malicious scripts. Employ context-aware output encoding (e.g., HTML entity encoding) when rendering attribute data in web pages to prevent script execution. Use Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of XSS attacks. Regularly audit and monitor web application logs for unusual input patterns or user behavior indicative of exploitation attempts. Educate users about phishing risks and encourage cautious interaction with links or inputs from untrusted sources. Additionally, consider deploying Web Application Firewalls (WAFs) with rules tailored to detect and block XSS payloads targeting nopCommerce attributes. Finally, maintain an incident response plan to quickly address any detected exploitation.
Description
nopCommerce 4.90.0 is vulnerable to Cross Site Scripting (XSS) via the Attributes functionality.