cve.bz

CVE-2010-3910 vtiger vtiger crm: Path traversal

no score yetEPSS 7.2%

vtiger vtiger crm: no CVSS score yet. EPSS 7.2% estimated probability of exploitation activity in the next 30 days.

On this page
Multiple directory traversal vulnerabilities in the return_application_language function in include/utils/utils.php in vtiger CRM before 5.2.1 allow remote attackers to include and execute arbitrary local files via a .. (dot dot) in (1) the lang_crm parameter to phprint.php or (2) the current_language parameter in an Accounts Import action to graph.php.
EPSS
7.2% (unchanged from 7.2% a week ago; 7.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 94th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2010-3910 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2010-3910?via=ask-ai-copy and https://cve.bz/cve/CVE-2010-3910?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2010-3910 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
vtiger:vtiger_crmthrough 5.2.0
vtiger:vtiger_crm1.0
vtiger:vtiger_crm2.0
vtiger:vtiger_crm2.0.1
vtiger:vtiger_crm2.1
vtiger:vtiger_crm3
vtiger:vtiger_crm3.0
vtiger:vtiger_crm3.0:beta
vtiger:vtiger_crm3.2
vtiger:vtiger_crm4
vtiger:vtiger_crm4:beta
vtiger:vtiger_crm4:rc1
vtiger:vtiger_crm4.0
vtiger:vtiger_crm4.0.1
vtiger:vtiger_crm4.2
vtiger:vtiger_crm4.2.4
vtiger:vtiger_crm5.0.0
vtiger:vtiger_crm5.0.2
vtiger:vtiger_crm5.0.3
vtiger:vtiger_crm5.0.4
vtiger:vtiger_crm5.0.4:rc
vtiger:vtiger_crm5.1.0
vtiger:vtiger_crm5.1.0:rc

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON