Vulnerability in e107 (CVE-2026-43935)
Summary
Vulnerability in e107 (CVE-2026-43935). Confidential information can be exposed externally. Exploitable via Host header. 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, a Host Header Injection vulnerability in the password reset page allows attackers to manipulate the Host header to generate password reset links pointing to attacker-controlled domains. This can lead to phishing attacks, account takeover, or other security risks. The severity is high, as the vulnerability affects a critical function related to user authentication. 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-43935 has been found in e107.
Attackers can target a specific entry point like Host header over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade e107 to 2.3.4 or later.
If unsure, ask your IT team or search "e107 CVE-2026-43935" on the vendor's site.
CVE-2026-43935 (e107) — CWE-20 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: Host header
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.
A vulnerability (CWE-20) exists in e107. Attackers reach the vulnerable code path via Host header without authentication.
Check the vendor advisory for the affected versions of e107. Attack surface: Host header.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
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
- patch github.com