How severe is CVE-2022-2060?

CVE-2022-2060 has a CVSS score of 8.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-2060?

CVE-2022-2060 affects the following packages: dolibarr/dolibarr (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2022-2060?

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

How do I detect CVE-2022-2060 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-2022-2060 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-2022-2060 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-2060, 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-2022-2060?

CVE-2022-2060 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 60th 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-2022-2060?

CVE-2022-2060 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-2022-2060 published, and has it been updated?

CVE-2022-2060 was published on June 13, 2022 and was last updated on October 28, 2026. 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

HIGH severity

CVE-2022-2060 — dolibarr

HIGHFix: dolibarr/dolibarr@2b5b995

CVE-2022-2060 is a high-severity (CVSS 8.4) 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.

Cross-site Scripting (XSS) - Stored in dolibarr/dolibarr

Also known asBIT-dolibarr-2022-2060GHSA-8fvr-7945-mg7w

Published

Jun 13, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs60th percentile — riskier than 60% 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

A Cross-site Scripting (XSS) vulnerability exists in the admin/accountant.php file. The fields town, name, and Accountant code can be used to escape double quote protection.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

dolibarr erp\/crmdolibarr

< 16.0.0

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.

Cross-site Scripting (XSS) - Stored in GitHub repository dolibarr/doliba…

huntr.devNVDJun 2022

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 16.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-2060 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

A Cross-site Scripting (XSS) vulnerability exists in the admin/accountant.php file. The fields `town`, `name`, and `Accountant code` can be used to escape double quote protection.

O3 Security · Impact-Aware SCA

Is CVE-2022-2060 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

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.

Timeline

Disclosed

Jun 13, 2022

First exploit

Jun 17, 2022

4 days after disclosure — rapid exploitation

Last updated

Oct 28, 2026

Identifiers

CVE-2022-2060

GHSA-8fvr-7945-mg7w

BIT-dolibarr-2022-2060

References

Advisorygithub.com · CVE 2022 2060.json Advisorynvd.nist.gov · CVE 2022 2060 Fixgithub.com · 2b5b9957c3010a5db9d1988c2efe5b209b16b47f Webhuntr.dev · 2acfc8fe 247c 4f88 aeaa 042b6b8690a0 Packagegithub.com · dolibarr

Related vulnerabilities

This CVE is high 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 verifiedOct 28, 2026

CVE-2022-2060 — dolibarr

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-2060 in your dependencies?