SSRF (Server-Side Request Forgery) in mosparo (CVE-2026-41195)
Summary
SSRF in mosparo (CVE-2026-41195). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.4.13 or later.
Original description
The description as published by the source.
mosparo is the modern solution to protect your online forms from spam. Prior to 1.4.13, the automatic rule package source URL feature allows a project member with the editor role to store an attacker-controlled URL that the server later fetches. Because the server follows http/https redirects and does not restrict private or loopback destinations, this becomes a stored SSRF primitive that can be turned into an internal HTTP probing oracle. This vulnerability is fixed in 1.4.13.
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-41195 has been found in mosparo.
Risk of unauthorized operations or information disclosure. CVSS score: 5.0/10.
What to do: upgrade mosparo to 1.4.13 or later.
If unsure, ask your IT team or search "mosparo CVE-2026-41195" on the vendor's site.
CVE-2026-41195 (mosparo) — CWE-918 / CVSS v3 5.0
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.4.13 — apply immediately
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.
SSRF (CWE-918) exists in mosparo.
Check the vendor advisory for the affected versions of mosparo.
Severity: Medium (CVSS 5.0/10). Risk of unauthorized operations or information disclosure.
Update to 1.4.13.
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 'mosparo' . 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 'mosparo' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mosparoを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mosparo to 1.4.13ステージング環境で 1.4.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov