Cross-Site Scripting (XSS) in YPTWallet plugin (CVE-2026-89249)
Summary
Cross-site scripting in YPTWallet plugin (CVE-2026-89249). Confidential information can be exposed externally.
Original description
The description as published by the source.
AVideo through commit c3edcc274c389816d434acadac07ee78eaf330c1 contains a stored cross-site scripting vulnerability in the YPTWallet plugin where user-supplied CryptoWallet values are base64-encoded but not HTML-escaped before storage in wallet_log.information. Administrators viewing pending withdrawal requests in pendingRequests.php execute the stored markup in their session, allowing attackers to perform administrative actions via same-origin fetch requests.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-2026-89249 has been found in YPTWallet plugin.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "YPTWallet plugin CVE-2026-89249" on the vendor's site.
CVE-2026-89249 (YPTWallet plugin) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
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 YPTWallet plugin.
Check the vendor advisory for the affected versions of YPTWallet plugin.
Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
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. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで YPTWallet plugin を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com
- web vulncheck.com
- web nvd.nist.gov
- web github.com