SSRF (Server-Side Request Forgery) in e107 (CVE-2026-43936)
Summary
SSRF in e107 (CVE-2026-43936). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.3.4 or later.
Original description
The description as published by the source.
e107 is a content management system (CMS). Prior to 2.3.4, you can access the local environment by specifying the URL of the local environment from "Image/File URL:" of "From a remote location" in "Media Manager" on the administrator screen. This vulnerability is fixed in 2.3.4.
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-43936 has been found in e107.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade e107 to 2.3.4 or later.
If unsure, ask your IT team or search "e107 CVE-2026-43936" on the vendor's site.
CVE-2026-43936 (e107) — CWE-918 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.3.4 — 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 e107.
Check the vendor advisory for the affected versions of e107.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.3.4.
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 'e107' . 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 'e107' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
e107を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade e107 to 2.3.4ステージング環境で 2.3.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com