LiveActive security incident?Get immediate response
CVE Record

CVE-2017-14240: There is a sensitive information disclosure vulnerability in document.php in Dolibarr ERP/CRM version 6.0.0...

There is a sensitive information disclosure vulnerability in document.php in Dolibarr ERP/CRM version 6.0.0 via the file parameter.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2017-14240 describes sensitive information disclosure in Dolibarr ERP/CRM 6.0.0. The issue is tied to document.php and its file parameter, meaning protected or unintended documents may be exposed if an affected instance is reachable.

Executive priority

Treat as a targeted legacy-system exposure check. Priority rises if Dolibarr 6.0.0 is internet-facing or stores contracts, invoices, customer data, or regulated information.

Technical view

The source bundle identifies a disclosure flaw in Dolibarr ERP/CRM 6.0.0 within document.php via the file parameter. No CVSS score, CWE, detailed affected CPEs, or confirmed fixed release are provided. A Dolibarr commit is the primary vendor-linked reference.

Likely exposure

Exposure is most likely for organizations still running Dolibarr ERP/CRM 6.0.0, especially internet-facing instances that store sensitive business documents or customer files.

Exploitation context

The bundle does not show CISA KEV listing or any cited evidence of active exploitation. Public evidence is limited to the CVE description and a Dolibarr commit reference.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or fixed version is included. Focus validation on version presence, document.php exposure, access-control behavior, and whether the vendor commit is incorporated.

Mitigation direction

  • Inventory Dolibarr deployments and identify any version 6.0.0 instances.
  • Check Dolibarr vendor guidance and release notes for the fixed version.
  • Upgrade affected installations once the vendor-supported fixed release is confirmed.
  • Restrict public access to document.php where business operations allow.
  • Review document permissions and remove unnecessary sensitive files from exposed paths.

Validation and detection

  • Confirm deployed Dolibarr versions across production and staging environments.
  • Verify whether the referenced Dolibarr commit or equivalent fix is present.
  • Review web logs for unusual document.php access patterns.
  • Check whether sensitive documents are accessible only to authorized users.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-14240 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.