# CVE-2020-13828: Dolibarr stored Cross-Site Scripting (XSS) vulnerability

> Authenticated attackers can inject arbitrary scripts via multiple parameters in Dolibarr, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** BIT-dolibarr-2020-13828, GHSA-8r2w-phx4-mgpv, UBUNTU-CVE-2020-13828

## What is CVE-2020-13828?

CVE-2020-13828 is a medium-severity cross-site scripting vulnerability in Dolibarr Dolibarr Erp\/Crm, published on 31 Aug 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Dolibarr 11.0.4 is affected by multiple stored Cross-Site Scripting (XSS) vulnerabilities that could allow remote authenticated attackers to inject arbitrary web script or HTML via ticket/card.php?action=create with the subject, message, or address parameter; adherents/card.php with the societe or address parameter; product/card.php with the label or customcode parameter; or societe/card.php with the alias or barcode parameter.

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

## Which versions are affected by CVE-2020-13828?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dolibarr/dolibarr` | Packagist | All versions to 11.0.4 | None |
| `dolibarr/dolibarr` | Packagist | All versions to 11.0.4 | None |
| `dolibarr` | Bitnami | From 11.0.4 to 11.0.4 | None |

Products: Dolibarr Dolibarr Erp\/Crm.

## How do I fix CVE-2020-13828?

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

## Is CVE-2020-13828 being exploited?

There is no known exploitation of CVE-2020-13828 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-2020-13828 and fix it if it is affected.

What it is: CVE-2020-13828 is a medium-severity cross-site scripting vulnerability in Dolibarr Dolibarr Erp\/Crm, published on 31 Aug 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-13828 in the wild and no public exploit code.

Affected packages and fixed versions:
- dolibarr/dolibarr (Packagist): affected all versions up to 11.0.4; no fix listed
- dolibarr/dolibarr (Packagist): affected all versions up to 11.0.4; no fix listed
- dolibarr (Bitnami): affected from 11.0.4 up to 11.0.4; 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-2020-13828/ (Markdown: https://insights.sbomify.com/CVE-2020-13828/index.md)
```

## Sources

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

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