dbcve.org
Vtiger CrmApplication · Vtiger

CVE-2025-1618

MEDIUM · 6.1 CVSS v3.1 Published 2025-02-24
Fix available
A fix is available. Upgrade to 7.0 or later.
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 vulnerability has been found in vTiger CRM 6.4.0/6.5.0 and classified as problematic. This vulnerability affects unknown code of the file /modules/Mobile/index.php. The manipulation of the argument _operation leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 7.0 is able to address this issue. It is recommended to upgrade the affected component.

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

Reflected XSS vulnerability in vTiger CRM's mobile module. The _operation parameter in /modules/Mobile/index.php is not properly sanitized, allowing injection of malicious JavaScript through the URL. This is a classic reflected XSS issue where user-supplied input in the _operation argument is echoed back in the response without encoding.

MitigationUpgrade vTiger CRM from versions 6.4.0/6.5.0 to version 7.0, which contains the fix. Alternatively, implement input validation/sanitization on the _operation parameter as a temporary measure until the upgrade can be performed.

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:>= 6.4.0, < 7.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 vTiger CRM installation
    Check for the presence of vtigercrm by examining the web root for vtiger CRM files, or access the application login page.
    Affected if vTiger CRM is installed and accessible on the server.
  2. Identify the installed vTiger CRM version
    Locate the version file or check the vtiger version constant - typically found in vtigerversion.php in the includes directory, or access /vtigercrm/ and look for version information in the login page footer.
    Affected if The installed version falls within >= 6.4.0 and < 7.0.
  3. Verify mobile module accessibility
    Attempt to access the /modules/Mobile/index.php endpoint via HTTP request (e.g., GET http://[host]/vtigercrm/modules/Mobile/index.php).
    Affected if The mobile module endpoint returns a 200 OK response, indicating it is enabled and accessible.
  4. Test _operation parameter for XSS vulnerability
    Send a crafted request to /modules/Mobile/index.php with a test payload in the _operation parameter (e.g., ?_operation=<script>alert(1)</script>), then examine if the response reflects the unsanitized input.
    Affected if The response contains the raw _operation parameter value without HTML encoding, indicating the vulnerability is present.
  5. Review web server logs for exploitation attempts
    Examine HTTP access logs for requests to /modules/Mobile/index.php containing suspicious patterns in the _operation parameter, such as <script>, javascript:, or other XSS vectors.
    Affected if Log entries show unauthenticated requests with malicious payloads in the _operation parameter.

The environment is affected if vTiger CRM version 6.4.0 through 6.x (below 7.0) is installed, the mobile module is accessible, and the _operation parameter reflects unsanitized user input in responses.

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
Upgrade available Upgrade to 7.0 or later
Fixed in 7.0
Interim mitigation

Upgrade vTiger CRM from versions 6.4.0/6.5.0 to version 7.0, which contains the fix. Alternatively, implement input validation/sanitization on the _operation parameter as a temporary measure until the upgrade can be performed.

Recommended fix High confidence

version 7.0

  1. Backup the existing Vtiger CRM database and files
  2. Review Vtiger 7.0 upgrade documentation for any pre-upgrade requirements
  3. Ensure the system meets the minimum requirements for version 7.0
  4. Perform a test upgrade in a staging environment first
  5. Execute the upgrade to Vtiger CRM version 7.0
  6. Verify the XSS vulnerability is resolved by testing the /modules/Mobile/index.php _operation parameter
  7. Confirm all core CRM functions work correctly after upgrade
Caveat Major version upgrades may introduce breaking changes; review Vtiger 7.0 release notes before upgrading

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

Fix this in Vtiger Crm Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA3.0 h
29.0 hours of engineering $5,100
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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