Path Traversal in github.com/casdoor/casdoor (CVE-2026-6815)
Summary
Path traversal in github.com/casdoor/casdoor (CVE-2026-6815). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
An arbitrary file write vulnerability exists in Casdoor's Local File System storage provider. Due to insufficient path sanitization, an authenticated attacker with administrative privileges can perform a Path Traversal attack to create or overwrite arbitrary files anywhere on the host filesystem, bypassing the application's intended storage sandbox.
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-6815 has been found in github.com/casdoor/casdoor.
Risk of unauthorized operations or information disclosure. CVSS score: 5.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "github.com/casdoor/casdoor CVE-2026-6815" on the vendor's site.
CVE-2026-6815 (github.com/casdoor/casdoor) — CWE-22 / CVSS v3 5.9
Attack vector: local / unauthenticated / no user interaction
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.
Path traversal (CWE-22) exists in github.com/casdoor/casdoor.
Check the vendor advisory for the affected versions of github.com/casdoor/casdoor.
Severity: Medium (CVSS 5.9/10). Risk of unauthorized operations or information disclosure.
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. Run grep -r 'github.com/casdoor/casdoor' . 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 'github.com/casdoor/casdoor' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/casdoor/casdoorを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- JVN JVNDB-2026-017319
- package github.com
- web kb.cert.org
- web kb.cert.org