# CVE-2017-17897: Dolibarr SQL injection vulnerability in comm/multiprix.php

> Remote attackers can execute arbitrary SQL commands via the id parameter in Dolibarr ERP/CRM, potentially compromising database integrity and confidentiality.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9v7m-f3cv-68rw, UBUNTU-CVE-2017-17897

## What is CVE-2017-17897?

CVE-2017-17897 is a critical SQL injection vulnerability in Dolibarr Dolibarr Erp\/Crm, published on 24 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in comm/multiprix.php in Dolibarr ERP/CRM version 6.0.4 allows remote attackers to execute arbitrary SQL commands via the id parameter.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2017-17897?

2 open source packages ship an affected version, including dolibarr/dolibarr. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dolibarr/dolibarr` | Packagist | All versions | 6.0.5 |
| `dolibarr/dolibarr` | Packagist | All versions | 6.0.5 |

Products: Dolibarr Dolibarr Erp\/Crm.

## How do I fix CVE-2017-17897?

Upgrade dolibarr/dolibarr to 6.0.5 or later.

## Is CVE-2017-17897 being exploited?

There is no known exploitation of CVE-2017-17897 in the wild and no public exploit code.

## Other vulnerabilities in Dolibarr Dolibarr Erp\/Crm

- [CVE-2022-43138](https://insights.sbomify.com/CVE-2022-43138/): Dolibarr vulnerable to privilege escalation (critical 9.8)
- [CVE-2022-40871](https://insights.sbomify.com/CVE-2022-40871/): Dolibarr vulnerable to Eval Injection (critical 9.8)
- [CVE-2021-33816](https://insights.sbomify.com/CVE-2021-33816/): Dolibarr remote PHP code execution (critical 9.8)
- [CVE-2020-7995](https://insights.sbomify.com/CVE-2020-7995/): Dolibarr Improper Restriction of Excessive Authentication Attempts (critical 9.8)
- [CVE-2013-2091](https://insights.sbomify.com/CVE-2013-2091/): SQL injection in dolibarr (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-17897 and fix it if it is affected.

What it is: CVE-2017-17897 is a critical SQL injection vulnerability in Dolibarr Dolibarr Erp\/Crm, published on 24 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-17897 in the wild and no public exploit code.

Affected packages and fixed versions:
- dolibarr/dolibarr (Packagist): affected all versions; fixed in 6.0.5
- dolibarr/dolibarr (Packagist): affected all versions; fixed in 6.0.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-17897/ (Markdown: https://insights.sbomify.com/CVE-2017-17897/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-17897
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-17897
- OSV: https://osv.dev/vulnerability/CVE-2017-17897

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-17897/
Summaries are generated and may contain mistakes; the official description above is the record.