How severe is CVE-2022-0602?

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

Which packages are affected by CVE-2022-0602?

CVE-2022-0602 affects the following packages: tastyigniter/tastyigniter (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2022-0602?

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

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

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

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

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

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

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

CVE-2022-0602 was published on April 5, 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-0602 — tastyigniter

HIGHFix: tastyigniter/tastyigniter@992d4ce

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

Cross-site Scripting (XSS) - DOM in tastyigniter/tastyigniter

Also known asGHSA-cjw5-f2x5-r4q5

Published

Apr 5, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

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

🐘tastyigniter/tastyigniter

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

TastyIgniter prior to version 3.3.0 is vulnerable to Document Object Model (DOM) based Cross-site Scripting (XSS).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`tastyigniter/tastyigniter`	all versions	3.3.0`composer require tastyigniter/tastyigniter:^3.3.0`

Affected Products

1 product · 1 configurations

Application

tastyignitertastyigniter

< 3.3.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) - DOM in GitHub repository tastyigniter/tasty…

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 tastyigniter/tastyigniter, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tastyigniter/tastyigniter to 3.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0602 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

TastyIgniter prior to version 3.3.0 is vulnerable to Document Object Model (DOM) based Cross-site Scripting (XSS).

O3 Security · Impact-Aware SCA

Is CVE-2022-0602 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

Low

Raw vector

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

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 5, 2022

First exploit

Apr 12, 2022

7 days after disclosure — rapid exploitation

Last updated

Oct 28, 2026

Identifiers

CVE-2022-0602

GHSA-cjw5-f2x5-r4q5

References

Advisorygithub.com · CVE 2022 0602.json Advisorynvd.nist.gov · CVE 2022 0602 Fixgithub.com · 992d4ce6444805c3132e3635a01b6fd222063554 Webhuntr.dev · 615f1788 d474 4580 b0ef 5edd50274010 Packagegithub.com · TastyIgniter

Related vulnerabilities

Also affects tastyigniter/tastyigniter

This CVE is high severity; 1 of 3 other CVEs affecting tastyigniter/tastyigniter is rated as high or higher (top: high).

CVE-2025-61417CVE-2024-44313CVE-2024-44314

Same weakness: CWE-79

This CVE is high severity; 3 of 5 other CVEs with CWE-79 are rated as high or higher (top: critical).

CVE-2026-55649CVE-2026-113787CVE-2026-44267CVE-2026-96632CVE-2026-9086Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026