How severe is CVE-2022-1380?

CVE-2022-1380 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-1380?

CVE-2022-1380 affects the following packages: snipe/snipe-it (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2022-1380?

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

How do I detect CVE-2022-1380 in my Packagist dependencies?

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

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

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

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

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

CVE-2022-1380 was published on April 16, 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

CRITICAL severity

CVE-2022-1380 — snipe-it

CRITICALFix: snipe/snipe-it@f211c11

CVE-2022-1380 is a critical-severity (CVSS 9.1) Cross-site Scripting (XSS) vulnerability in snipe/snipe-it. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for snipe/snipe-it — see the affected versions and patch details below.

Stored Cross Site Scripting vulnerability in Item name parameter in snipe/snipe-it

Also known asGHSA-p885-prv3-m4xv

Published

Apr 16, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

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

🐘snipe/snipe-it

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

Stored Cross Site Scripting vulnerability in Item name parameter in GitHub repository snipe/snipe-it prior to v5.4.3. The vulnerability is capable of stolen the user Cookie.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`snipe/snipe-it`	all versions	5.4.3`composer require snipe/snipe-it:^5.4.3`

Affected Products

1 product · 1 configurations

Application

snipe-itsnipeitapp

< 5.4.3

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.

Stored Cross Site Scripting vulnerability in Item name parameter in GitH…

huntr.devNVDApr 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for snipe/snipe-it, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update snipe/snipe-it to 5.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-1380 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

Stored Cross Site Scripting vulnerability in Item name parameter in GitHub repository snipe/snipe-it prior to v5.4.3. The vulnerability is capable of stolen the user Cookie.

O3 Security · Impact-Aware SCA

Is CVE-2022-1380 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

High

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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

Apr 16, 2022

First exploit

Apr 25, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-1380

GHSA-p885-prv3-m4xv

References

Advisorygithub.com · CVE 2022 1380.json Advisorynvd.nist.gov · CVE 2022 1380 Fixgithub.com · f211c11034baf4281aa62e7b5e0347248d995ee9 Webhuntr.dev · 3d45cfca 3a72 4578 b735 98837b998a12 Packagegithub.com · snipe it

Related vulnerabilities

This CVE is critical severity — higher than any of the other 8 CVEs affecting snipe/snipe-it (highest there: high).

CVE-2026-63498CVE-2026-63493CVE-2026-62368CVE-2026-55515CVE-2026-55476CVE-2026-55516CVE-2026-55475CVE-2026-55479

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-1380 — snipe-it

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-1380 in your dependencies?