Security readout for executives and security teams
Plain-English summary
Dolibarr ERP/CRM versions before 5.0.3 contain a SQL injection flaw in the user management area. For a business, the concern is possible unauthorized database access or manipulation if an affected instance is reachable. The sources do not provide a CVSS score or confirmed exploitation.
Executive priority
Treat as a priority legacy-application risk if Dolibarr is still used. SQL injection in ERP/CRM software can affect sensitive business data, but urgency depends on whether vulnerable versions remain deployed.
Technical view
CVE-2017-9435 is a SQL injection in Dolibarr ERP/CRM before 5.0.3, affecting user/index.php parameters search_supervisor and search_statut. The public record names the vulnerable parameters but does not specify authentication requirements, exploit complexity, or database impact scope.
Likely exposure
Exposure is most likely in organizations still running Dolibarr ERP/CRM before 5.0.3 with user/index.php reachable to users or the internet.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Public details are limited to the affected version range, vulnerable file, parameters, and vendor references.
Researcher notes
Evidence is sparse: no CVSS vector, CWE, exploit prerequisites, or confirmed exploitation are included. Focus validation on versioning, reachability of user/index.php, and whether the vendor fix is present.
Mitigation direction
- Upgrade Dolibarr ERP/CRM to version 5.0.3 or later.
- Review the vendor commit and ChangeLog for the relevant fix details.
- Restrict access to Dolibarr user-management pages until patched.
- Monitor database and application logs for suspicious user-search activity.
Validation and detection
- Inventory Dolibarr deployments and record exact running versions.
- Confirm no production instance is below version 5.0.3.
- Verify user/index.php is not exposed beyond intended users.
- Check change records for the referenced vendor fix or later release.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
Database behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-9435 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Dolibarr/dolibarr/commit/70636cc59ffa1ffbc0ce3dba315d7d9b837aad04CVE reference · x_refsource_CONFIRM
- https://github.com/Dolibarr/dolibarr/blob/develop/ChangeLogCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.