Cross-Site Scripting (XSS) in @yaireo/tagify (CVE-2022-25854)
Summary
Cross-site scripting in @yaireo/tagify (CVE-2022-25854). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.9.8 or later.
Original description
The description as published by the source.
This affects the package @yaireo/tagify before 4.9.8. The package is used for rendering UI components inside the input or text fields, and an attacker can pass a malicious placeholder value to it to fire the XSS payload.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2022-25854 has been found in @yaireo/tagify.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @yaireo/tagify to 4.9.8 or later.
If unsure, ask your IT team or search "@yaireo/tagify CVE-2022-25854" on the vendor's site.
CVE-2022-25854 (@yaireo/tagify) — CWE-79
Attack vector: remote (network-reachable) / unauthenticated
Patched: 4.9.8 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in @yaireo/tagify.
Check the vendor advisory for the affected versions of @yaireo/tagify.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.9.8.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@yaireo/tagify' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@yaireo/tagify' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@yaireo/tagifyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @yaireo/tagify to 4.9.8ステージング環境で 4.9.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory snyk.io
- advisory github.com
- package github.com
- patch github.com
- report github.com
- web bsg.tech
- web github.com
- web bsg.tech