dbcve.org
Vtiger CrmApplication · Vtiger

CVE-2025-45755

MEDIUM · 6.1 CVSS v3.1 Published 2025-05-21
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
A Stored Cross-Site Scripting (XSS) vulnerability exists in Vtiger CRM Open Source Edition v8.3.0, exploitable via the Services Import feature. An attacker can craft a malicious CSV file containing an XSS payload, mapped to the Service Name field. When the file is uploaded, the application improperly sanitizes user input, leading to persistent script execution.

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 · moderate confidence

A Stored Cross-Site Scripting (XSS) vulnerability in Vtiger CRM Open Source Edition v8.3.0 allows attackers to inject malicious scripts via the Services Import feature. Attackers craft a CSV file containing XSS payloads in the Service Name field; upon upload, the application fails to properly sanitize this input, causing the payload to be stored and executed persistently when other users view the imported data.

MitigationImplement proper input validation and output encoding for all CSV import fields, specifically the Service Name field. Apply context-appropriate escaping when displaying imported data to prevent script execution.

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
Vtiger CrmApplication
Affected:= 8.3.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. Verify Vtiger CRM version
    Log into Vtiger CRM as admin and navigate to Settings > CRM Settings > Server Information, or check the version displayed in the application footer
    Affected if The installed version is exactly 8.3.0
  2. Confirm Services module is accessible
    Log in as a user with access to the Services module and verify the module appears in the main navigation menu
    Affected if The Services module is present and accessible in the application
  3. Check for Services Import feature
    Navigate to the Services module, look for an Import button or menu option typically found in the module toolbar
    Affected if The Import functionality exists and is available for the Services module
  4. Inspect Service records for XSS payloads
    In the Services module list view, examine the Service Name column for any unexpected characters such as <script>, javascript:, onerror=, or other HTML/JS code patterns
    Affected if Any Service records contain executable script tags or event handlers in the Service Name field that could trigger XSS when viewed

A user is affected if they are running Vtiger CRM version 8.3.0, have access to the Services module, and have imported CSV data containing unsanitized Service Name values that contain script execution code.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding for all CSV import fields, specifically the Service Name field. Apply context-appropriate escaping when displaying imported data to prevent script execution.

Recommended fix Moderate confidence

Vtiger CRM Open Source v8.4.0 or later (latest stable release)

  1. 1. Navigate to the official Vtiger CRM download page or your instance admin panel
  2. 2. Check for the latest stable release (v8.4.0 or later) that includes the security fix for CVE-2025-45755
  3. 3. Backup your current Vtiger CRM database and configuration files
  4. 4. Download the latest Vtiger CRM Open Source Edition package
  5. 5. Follow the standard Vtiger upgrade documentation to apply the update
  6. 6. After upgrade, verify the Services Import functionality works correctly
  7. 7. Confirm the XSS payload from the original proof-of-concept no longer executes
Caveat Review Vtiger release notes for any breaking changes between v8.3.0 and the target version; test in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vtiger Crm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-45755 — 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-45755 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