dbcve.org
NopcommerceApplication

CVE-2025-65592

MEDIUM · 6.1 CVSS v3.1 Published 2025-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
nopCommerce 4.90.0 is vulnerable to Cross Site Scripting (XSS) in the product management functionality. Malicious payloads inserted into the "Product Name" and "Short Description" fields are stored in the backend database and executed automatically whenever a user views the affected pages.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

nopCommerce 4.90.0 contains a stored Cross-Site Scripting (XSS) vulnerability in the product management module. Attackers with admin access can inject malicious JavaScript payloads into the Product Name and Short Description fields, which persist in the database. When other users view the affected product pages, the embedded scripts execute in their browsers, potentially enabling session hijacking or credential theft.

MitigationImplement output encoding and input validation for the Product Name and Short Description fields in the product management functionality to neutralize malicious script payloads before storage and rendering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NopcommerceApplication
Affected:= 4.90.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm nopCommerce version
    Navigate to Administration > Configuration > Log or check the ~/bin/AssemblyInfo.cs file for the version number. The vulnerability affects only version 4.90.0.
    Affected if The installed version is exactly 4.90.0
  2. Locate product database table
    Access the nopCommerce database (typically in SQL Server or MySQL) and identify the product table, commonly named 'Product' or 'Nop_Product'. Identify fields for 'Name' and 'ShortDescription'.
    Affected if The product table with Name and ShortDescription fields exists and is accessible
  3. Inspect Product Name and Short Description fields for script tags
    Run a SQL query to select records containing HTML script tags, JavaScript event handlers (onerror, onload, onclick), or javascript: URIs in the Name and ShortDescription columns. Example: SELECT Id, Name, ShortDescription FROM Product WHERE Name LIKE '%<script%' OR ShortDescription LIKE '%<script%' OR Name LIKE '%onerror%'
    Affected if Any product records contain unsanitized HTML script tags or JavaScript event handlers in Name or ShortDescription fields
  4. Verify if encoding is applied on product page render
    View the HTML source of a product detail page in the storefront. Check if the Product Name and Short Description are rendered with HTML encoding (e.g., &lt;script&gt; instead of <script>).
    Affected if The product page renders Product Name or Short Description without HTML encoding, allowing script execution
  5. Test for XSLT or meta tag injection in product fields
    Search the database for characters like <, >, & that may indicate lack of output encoding when rendering product data in the frontend.
    Affected if Product fields contain raw HTML/JS characters that render unescaped in the browser

You are affected if running nopCommerce version 4.90.0 AND the product database contains unencoded HTML/JavaScript in the Product Name or Short Description fields that renders as executable code in the storefront.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement output encoding and input validation for the Product Name and Short Description fields in the product management functionality to neutralize malicious script payloads before storage and rendering.

Fix this in Nopcommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-65592 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-65592 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data