← Back
CVE-2026-40353
Cross-Site Scripting (XSS) in wger (CVE-2026-40353)
Summary
cross-site scripting in wger (CVE-2026-40353). Risk of unauthorized operations or information disclosure. Exploitable via ``AbstractLicenseModel.attribution_link``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-40353** has been found in wger.
Attackers can target a specific entry point like ``AbstractLicenseModel.attribution_link`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "wger CVE-2026-40353" on the vendor's site.
CVE-2026-40353 (wger) — CWE-79 /
Attack vector: remote (network-reachable)
Attack surface: `AbstractLicenseModel.attribution_link` / `license_author` / `license_title` / `license_object_url`
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.
❓ What is the problem
**Cross-site scripting (XSS)** (CWE-79) exists in wger. Attackers reach the vulnerable code path via ``AbstractLicenseModel.attribution_link`` without authentication.
📍 Affected scope
wger — . Attack surface: `AbstractLicenseModel.attribution_link` / `license_author` / `license_title` / `license_object_url`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'wger' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'wger' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `wger` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
wger
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"2.4"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-40353
- advisory https://github.com/advisories/GHSA-6f54-qjvm-wwq3
- package https://github.com/wger-project/wger
- package https://pypi.org/project/wger
- web https://github.com/wger-project/wger/security/advisories/GHSA-6f54-qjvm-wwq3
- web https://github.com/wger-project/wger/releases/tag/2.5