Vulnerability in lamp-cloud (CVE-2026-94535)
Summary
Vulnerability in lamp-cloud (CVE-2026-94535). Data can be tampered with by attackers. Exploitable via DELETE /anyone/extendNotice/deleteMyNotice.
Original description
The description as published by the source.
lamp-cloud through 5.10.0 contains an authorization bypass vulnerability in the deleteMyNotice endpoint that allows authenticated users to delete other users' notifications. Attackers can call the DELETE /anyone/extendNotice/deleteMyNotice endpoint with arbitrary notice IDs to permanently remove notifications belonging to other users without recipient validation.
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-94535 has been found in lamp-cloud.
Attackers can target a specific entry point like DELETE /anyone/extendNotice/deleteMyNotice over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "lamp-cloud CVE-2026-94535" on the vendor's site.
CVE-2026-94535 (lamp-cloud) — CWE-639 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: DELETE /anyone/extendNotice/deleteMyNotice
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) exists in lamp-cloud. Attackers reach the vulnerable code path via DELETE /anyone/extendNotice/deleteMyNotice.
Check the vendor advisory for the affected versions of lamp-cloud. Attack surface: DELETE /anyone/extendNotice/deleteMyNotice.
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.
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 /anyone/extendNotice/deleteMyNotice requests with malformed payloads or SQL meta-characters. Run grep -r 'lamp-cloud' . 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 'lamp-cloud' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
lamp-cloudを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'DELETE /anyone/extendNotice/deleteMyNotice' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
DELETE /anyone/extendNotice/deleteMyNoticeへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against DELETE /anyone/extendNotice/deleteMyNotice on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web github.com
- web github.com
- web github.com
- web vulncheck.com
- web nvd.nist.gov
- web github.com