← Back
CVE-2026-63220
medium
CVSS 4.8
Vulnerability in codeigniter4/framework (CVE-2026-63220)
Summary
vulnerability in codeigniter4/framework (CVE-2026-63220). Risk of unauthorized operations or information disclosure. Exploitable via ``forceGlobalSecureRequests``. Mitigation: upgrade to `4.7.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-63220** has been found in codeigniter4/framework.
Attackers can target a specific entry point like ``forceGlobalSecureRequests`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/10.
What to do: upgrade codeigniter4/framework to **4.7.4** or later.
If unsure, ask your IT team or search "codeigniter4/framework CVE-2026-63220" on the vendor's site.
CVE-2026-63220 (codeigniter4/framework) — CWE-348 / CVSS v3 4.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `forceGlobalSecureRequests`
Patched: `4.7.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.
❓ What is the problem
**A vulnerability** (CWE-348) exists in codeigniter4/framework. Attackers reach the vulnerable code path via ``forceGlobalSecureRequests`` without authentication.
📍 Affected scope
codeigniter4/framework — . Attack surface: `forceGlobalSecureRequests`.
🔥 Severity
Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.7.4**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'codeigniter4/framework' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'codeigniter4/framework' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `codeigniter4/framework` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade codeigniter4/framework to 4.7.4ステージング環境で 4.7.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
codeigniter4/framework
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.7.4"}]}]
References
- web https://github.com/codeigniter4/CodeIgniter4/commit/ecbf044666bed41d23f07518096d9843fe6c08b0
- web https://github.com/codeigniter4/CodeIgniter4/releases/tag/v4.7.4
- web https://github.com/codeigniter4/CodeIgniter4/security/advisories/GHSA-7wmf-pw8j-mc78
- web https://nvd.nist.gov/vuln/detail/CVE-2026-63220
- web https://github.com/advisories/GHSA-7wmf-pw8j-mc78