How severe is CVE-2016-1912?

CVE-2016-1912 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2016-1912?

CVE-2016-1912 affects the following packages: dolibarr/dolibarr (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2016-1912?

The records we use list no patched version of dolibarr/dolibarr for CVE-2016-1912. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

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

Yes. There are 3 known exploit references for CVE-2016-1912, including 3 in-the-wild exploitations 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-2016-1912?

CVE-2016-1912 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 72th 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-2016-1912?

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

CVE-2016-1912 was published on January 15, 2016 and was last updated on October 20, 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

MEDIUM severity

CVE-2016-1912 — dolibarr

MEDIUMFix: GPCsolutions/dolibarr@0d31813

CVE-2016-1912 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in dolibarr/dolibarr. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Dolibarr ERP and CRM contain XSS Vulnerabilities

Also known asGHSA-jh5p-wpg2-8rgv

Published

Jan 15, 2016

Updated

Oct 20, 2026

Affected

1 pkg

Patched

See advisory

Exploits

3 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

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

Multiple cross-site scripting (XSS) vulnerabilities in Dolibarr ERP/CRM 3.8.3 allow remote authenticated users to inject arbitrary web script or HTML via the (1) lastname, (2) firstname, (3) email, (4) job, or (5) signature parameter to htdocs/user/card.php.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`dolibarr/dolibarr`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

dolibarrdolibarr

≤ 3.8.2

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.

Multiple cross-site scripting (XSS) vulnerabilities in Dolibarr ERP/CRM …

packetstormsecurity.comNVDJan 2016

Report on information-security.fr

information-security.frNVDJan 2016

Report on github.com

github.comNVDJan 2016

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.
Remediation status
The records we use list no patched version of dolibarr/dolibarr for CVE-2016-1912. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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

O3 Security · Impact-Aware SCA

Is CVE-2016-1912 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:L/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. 3 public proof-of-concept references are listed on this page.

Timeline

Disclosed

Jan 15, 2016

First exploit

Jan 22, 2016

6 days after disclosure — rapid exploitation

Last updated

Oct 20, 2026

Identifiers

CVE-2016-1912

GHSA-jh5p-wpg2-8rgv

References

Advisorynvd.nist.gov · CVE 2016 1912 Fixgithub.com · 0d3181324c816bdf664ca5e1548dfe8eb05c54f8 Webtwitter.com Webinformation-security.fr · xss dolibarr version 3 8 3 Evidencepacketstormsecurity.com · Dolibarr 3.8.3 Cross Site Scripting Evidenceinformation-security.fr · xss dolibarr version 3 8 3 Evidencegithub.com

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 verifiedOct 20, 2026