How severe is GHSA-2v3r-gvq5-qqgh?

No CVSS score has been assigned to GHSA-2v3r-gvq5-qqgh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2v3r-gvq5-qqgh?

GHSA-2v3r-gvq5-qqgh affects the following packages: dolibarr/dolibarr (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-2v3r-gvq5-qqgh?

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

How do I detect GHSA-2v3r-gvq5-qqgh 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 GHSA-2v3r-gvq5-qqgh 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 GHSA-2v3r-gvq5-qqgh actively exploited in the wild?

No public exploit code has been indexed for GHSA-2v3r-gvq5-qqgh yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-2v3r-gvq5-qqgh?

GHSA-2v3r-gvq5-qqgh has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 50th 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 GHSA-2v3r-gvq5-qqgh?

GHSA-2v3r-gvq5-qqgh 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 GHSA-2v3r-gvq5-qqgh published, and has it been updated?

GHSA-2v3r-gvq5-qqgh was published on January 27, 2025 and was last updated on April 3, 2025. 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

Dolibarr Cross-site Scripting vulnerabilityGHSA-2v3r-gvq5-qqgh

Fix: Dolibarr/dolibarr@56710ce

GHSA-2v3r-gvq5-qqgh is a Cross-site Scripting (XSS) vulnerability in dolibarr/dolibarr. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asBIT-dolibarr-2024-55227CVE-2024-55227

Published

Jan 27, 2025

Updated

Apr 3, 2025

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2v3r-gvq5-qqgh.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk+0.02%

Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk

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

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 in the Events/Agenda module of Dolibarr v21.0.0-beta allows attackers to execute arbitrary web scripts or HTMl via a crafted payload injected into the Title parameter.

Affected Packages

1 total

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

Affected Products

1 product · 1 configurations

Application

dolibarr erp\/crmdolibarr

1 version

21.0.0

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 GHSA-2v3r-gvq5-qqgh. 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 GHSA-2v3r-gvq5-qqgh in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works