Command Injection in SabyasachiRana WebMap (CVE-2026-90843)
Summary
Command injection in SabyasachiRana WebMap (CVE-2026-90843). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
A security vulnerability has been detected in SabyasachiRana WebMap up to 8b95fe4dc301a3c09ddf145b895de0bf9f8d2a25. This affects the function nmap_newscan of the file functions_nmap.py of the component New Nmap Scan Handler. Such manipulation of the argument target/params leads to os command injection. The attack may be launched remotely. The exploit has been disclosed publicly and may be used. The name of the patch is 3d52f65803a2716bff14d938352c6fef45b0cfb6. A patch should be applied to remediate this issue. This issue got fixed with a silent patch.
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-90843 has been found in SabyasachiRana WebMap.
Risk of unauthorized operations or information disclosure. CVSS score: 8.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "SabyasachiRana WebMap CVE-2026-90843" on the vendor's site.
CVE-2026-90843 (SabyasachiRana WebMap) — CWE-77 / CVSS v3 8.3
Attack vector: remote (network-reachable) / 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.
A vulnerability (CWE-77) exists in SabyasachiRana WebMap.
Check the vendor advisory for the affected versions of SabyasachiRana WebMap.
Severity: High (CVSS 8.3/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. 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・依存マニフェストで SabyasachiRana WebMap を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web calledstriker.gitbook.io
- web cna@vuldb.com
- web github.com
- web raw.githubusercontent.com
- web vuldb.com
- web vuldb.com
- web vuldb.com
- web vuldb.com
- web nvd.nist.gov
- web github.com
- web github.com