Security readout for executives and security teams
Plain-English summary
Dolibarr ERP/CRM 7.0.3 has a reported SQL injection in product/card.php through the statut parameter. In business terms, a vulnerable CRM or ERP instance could allow database manipulation or data access. The provided sources do not show active exploitation, CVSS scoring, or a named fixed release.
Executive priority
Treat this as a high-priority legacy ERP/CRM exposure if Dolibarr 7.0.3 is present. The business concern is database integrity and confidentiality, but urgency depends on whether affected systems are internet-facing or accessible by untrusted users.
Technical view
CVE-2018-13447 describes remote SQL injection in Dolibarr ERP/CRM 7.0.3, affecting product/card.php via the statut parameter. The referenced Dolibarr commit appears relevant to correction, but the source bundle does not state authentication requirements, fixed versions, or exploitation prerequisites.
Likely exposure
Exposure is likely limited to organizations still running Dolibarr ERP/CRM 7.0.3, especially if the application is reachable from untrusted networks. The source bundle does not identify other affected versions or products.
Exploitation context
The CVE record says remote attackers can execute arbitrary SQL commands. There is no KEV listing and no cited evidence of active exploitation in the provided source bundle.
Researcher notes
The provided evidence is sparse: no CVSS vector, CWE, authentication detail, exploit confirmation, or explicit fixed release is included. Analysis should stay anchored to Dolibarr 7.0.3 and the statut parameter unless vendor documentation proves broader scope.
Mitigation direction
- Inventory Dolibarr deployments and identify any version 7.0.3 systems.
- Check Dolibarr vendor guidance and release notes for the fixed upgrade path.
- Review the linked Dolibarr commit before considering any code-level backport.
- Restrict untrusted access to Dolibarr until patched or upgraded.
- Prioritize database backup and recovery readiness for exposed ERP/CRM systems.
Validation and detection
- Confirm whether any Dolibarr instance reports version 7.0.3.
- Verify whether product/card.php includes the linked upstream correction.
- Review web logs for unusual product/card.php requests involving statut.
- Review database logs for unexpected errors around the affected endpoint.
- Confirm exposed instances are patched, upgraded, or network-restricted.
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-2018-13447 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/36402c22eef49d60edd73a2f312f8e28fe0bd1cbCVE reference · x_refsource_MISC
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.