CVE-2010-3910
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 · uneditedMultiple 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.
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 confidenceDirectory traversal vulnerability in vtiger CRM's return_application_language function in include/utils/utils.php allows remote attackers to include arbitrary local files via .. sequences in the lang_crm parameter to phprint.php or current_language parameter in graph.php, enabling potential code 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<= 5.2.0= 1.0= 2.0= 2.0.1= 2.1= 3= 3.0= 3.2= 4= 4.0= 4.0.1= 4.2CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify vtiger CRM versionLocate the version file or check the version string in the vtiger installation - commonly found in includes/config.php, version.php, or in the About section of the application admin panelAffected if Installed version is 5.2.0 or earlier, or matches one of these: 1.0, 2.0, 2.0.1, 2.1, 3, 3.0, 3.2, 4, 4.0, 4.0.1, 4.2
-
Verify vulnerable script files existCheck if phprint.php exists in the web-accessible root directory of the vtiger installation, and check if graph.php exists in the root or include directoryAffected if Either phprint.php or graph.php file is present in the vtiger web directory
-
Inspect the vulnerable function codeExamine include/utils/utils.php and locate the return_application_language function - verify it uses the lang_crm or current_language parameter without sanitizing .. sequencesAffected if The function exists and processes the lang_crm or current_language parameter without validating for directory traversal sequences
-
Confirm web exposure of vulnerable endpointsVerify that phprint.php and graph.php are accessible via HTTP/HTTPS from the web server - attempt a test request or check web server configuration for rewrite rules that may block or allow these filesAffected if The vulnerable scripts are accessible over the network without authentication
A system is affected if it runs a vtiger CRM version in the affected list, has the vulnerable phprint.php or graph.php files accessible, and the return_application_language function is present and processes user-supplied language parameters.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to vtiger CRM 5.2.1 or later; implement strict input validation on the lang_crm and current_language parameters to reject .. sequences; consider disabling PHP's allow_url_include.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2010-3910 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-3910 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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