LingGuo-Drama through commit 8a6924a contains an insecure direct object reference vulnerability...
Summary
Vulnerability reported (CVE-2026-111722). Confidential information can be exposed externally. Exploitable via DELETE /admin/v1/projects/.
Original description
The description as published by the source.
LingGuo-Drama through commit 8a6924a contains an insecure direct object reference vulnerability that allows registered users to access other users' projects because projects.Get lacks an owner check. Self-registered attackers can iterate numeric IDs via GET, PUT and DELETE /admin/v1/projects/:id to read, overwrite, reassign or delete any user's short-drama projects.
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-111722 has been found.
Attackers can target a specific entry point like DELETE /admin/v1/projects/ over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-111722" on the vendor's site.
CVE-2026-111722 — CWE-639 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: DELETE /admin/v1/projects/
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-639) has been reported. Attackers reach the vulnerable code path via DELETE /admin/v1/projects/.
Check the vendor advisory for the affected versions. Attack surface: DELETE /admin/v1/projects/.
Severity: High (CVSS 8.1/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 DELETE /admin/v1/projects/ requests with malformed payloads or SQL meta-characters. 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・依存マニフェストで影響コンポーネントを特定する。
-
2Hunt for indicators of compromise detect
grep 'DELETE /admin/v1/projects/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
DELETE /admin/v1/projects/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against DELETE /admin/v1/projects/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web hackmd.io
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com