How severe is CVE-2019-19211?

CVE-2019-19211 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-19211?

CVE-2019-19211 affects the following packages: dolibarr/dolibarr (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2019-19211?

Update dolibarr/dolibarr to 10.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-19211 is resolved across your whole dependency graph.

How do I detect CVE-2019-19211 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dolibarr/dolibarr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-19211 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2019-19211 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2019-19211, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-19211?

CVE-2019-19211 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 77th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-19211?

CVE-2019-19211 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2019-19211 published, and has it been updated?

CVE-2019-19211 was published on May 24, 2022 and was last updated on February 22, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2019-19211 — dolibarr

MEDIUM

CVE-2019-19211 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in dolibarr/dolibarr. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for dolibarr/dolibarr — see the affected versions and patch details below.

Dolibarr ERP and CRM contain XSS Vulnerability

Published

May 24, 2022

Updated

Feb 22, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘dolibarr/dolibarr

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Dolibarr ERP/CRM before 10.0.3 has an Insufficient Filtering issue that can lead to user/card.php XSS.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`dolibarr/dolibarr`	all versions	10.0.3`composer require dolibarr/dolibarr:^10.0.3`

Affected Products

1 product · 1 configurations

Application

dolibarrdolibarr

≥ 3.0.0 && < 10.0.4

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Dolibarr ERP/CRM before 10.0.3 has an Insufficient Filtering issue that …

herolab.usd.deNVDMar 2020

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dolibarr/dolibarr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dolibarr/dolibarr to 10.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-19211 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Dolibarr ERP/CRM before 10.0.3 has an Insufficient Filtering issue that can lead to user/card.php XSS.

O3 Security · Impact-Aware SCA

Is CVE-2019-19211 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

dolibarr

5.7/10

Code-Review3/10

Maintained10/10

Branch-Protection3/10

Assessed Oct 26, 2026

Timeline

First exploit

Mar 18, 2020

Disclosed

May 24, 2022

Last updated

Feb 22, 2024

Identifiers

CVE-2019-19211

References

Advisorynvd.nist.gov · CVE 2019 19211 Webherolab.usd.de · usd 2019 0053 Webdolibarr.org · dolibarr changelogs Packagegithub.com · dolibarr

Related vulnerabilities

This CVE is medium severity; 5 of 8 other CVEs affecting dolibarr/dolibarr are rated as high or higher (top: critical).

CVE-2026-33944CVE-2026-10215CVE-2018-25357CVE-2026-7689CVE-2026-7688CVE-2026-31018CVE-2026-31019CVE-2026-23500

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 22, 2024