Vulnerability in wooey (CVE-2026-7142)
Summary
Vulnerability in wooey (CVE-2026-7142). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.13.3rc1 or later.
Original description
The description as published by the source.
A vulnerability was determined in Wooey up to 0.13.2. The impacted element is the function add_or_update_script of the file wooey/api/scripts.py of the component API Endpoint. Executing a manipulation can lead to improper authorization. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version 0.13.3rc1 and 0.14.0 is sufficient to resolve this issue. This patch is called f7846fc0c323da8325422cab32623491757f1b88. The affected component should be upgraded.
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-2026-7142 has been found in wooey.
Risk of unauthorized operations or information disclosure.
What to do: upgrade wooey to 0.13.3rc1 or later.
If unsure, ask your IT team or search "wooey CVE-2026-7142" on the vendor's site.
CVE-2026-7142 (wooey) — CWE-266
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.13.3rc1 — 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.
A vulnerability (CWE-266) exists in wooey.
Check the vendor advisory for the affected versions of wooey.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.13.3rc1.
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 'wooey' . 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 'wooey' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
wooeyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade wooey to 0.13.3rc1ステージング環境で 0.13.3rc1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web vuldb.com
- web vuldb.com
- web vuldb.com