# CVE-2019-19212: Dolibarr Cross-site Scripting via the qty parameter in product/fournisseurs.php

> Attackers can inject malicious scripts via the qty parameter in the product price screen, potentially leading to session hijacking or code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** No
- **Published:** 16 Mar 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pm57-926c-28mr, UBUNTU-CVE-2019-19212

## What is CVE-2019-19212?

CVE-2019-19212 is a critical cross-site scripting vulnerability in n/a, published on 16 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dolibarr ERP/CRM 3.0 through 10.0.3 allows XSS via the qty parameter to product/fournisseurs.php (product price screen).

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2019-19212?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dolibarr/dolibarr` | Packagist | From 3.0 to 10.0.3 | None |
| `dolibarr/dolibarr` | Packagist | From 3.0 to 10.0.3 | None |

Products: Dolibarr Dolibarr.

## How do I fix CVE-2019-19212?

No fix has been published for CVE-2019-19212 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-19212 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-16809](https://insights.sbomify.com/CVE-2018-16809/): Dolibarr SQL injection via the integer parameters qty and value_unit (critical 9.8)
- [CVE-2018-10094](https://insights.sbomify.com/CVE-2018-10094/): Dolibarr SQL injection vulnerability (critical 9.8)
- [CVE-2018-9019](https://insights.sbomify.com/CVE-2018-9019/): Dolibarr SQL Injection vulnerability (critical 9.8)
- [CVE-2017-14238](https://insights.sbomify.com/CVE-2017-14238/): Dolibarr SQL injection vulnerability in admin/menus/edit.php (critical 9.8)
- [CVE-2017-14242](https://insights.sbomify.com/CVE-2017-14242/): Dolibarr SQL injection vulnerability in don/list.php (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-19212 and fix it if it is affected.

What it is: CVE-2019-19212 is a critical cross-site scripting vulnerability in n/a, published on 16 Mar 2020. 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-2019-19212 in the wild and no public exploit code.

Affected packages and fixed versions:
- dolibarr/dolibarr (Packagist): affected from 3.0 up to 10.0.3; no fix listed
- dolibarr/dolibarr (Packagist): affected from 3.0 up to 10.0.3; no fix listed

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-2019-19212/ (Markdown: https://insights.sbomify.com/CVE-2019-19212/index.md)
```

## Sources

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

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