Path Traversal in cakephp/cakephp (CVE-2026-48820)
Summary
Path traversal in cakephp/cakephp (CVE-2026-48820). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.5.11 or later.
Original description
The description as published by the source.
CakePHP is a rapid development framework for PHP. In versions 4.5.11 and earlier, 4.6.0 through 4.6.3, 5.0.0 through 5.1.6, 5.2.0 through 5.2.12, and 5.3.0 through 5.3.5, View::_getElementFileName() does not check that the resolved element path is within the application/plugin view template paths. When element names are created with specifically crafted user-supplied data this weakness can be leveraged to include other PHP files on the server. Patched releases are available in 5.3.6, 5.2.13, 5.1.7, 4.6.4, and 4.5.11.
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-48820 has been found in cakephp/cakephp.
Risk of unauthorized operations or information disclosure.
What to do: upgrade cakephp/cakephp to 4.5.11 or later.
If unsure, ask your IT team or search "cakephp/cakephp CVE-2026-48820" on the vendor's site.
CVE-2026-48820 (cakephp/cakephp) — CWE-22
Patched: 4.5.11 — apply immediately
Workaround: If developers are not using user-supplied data in element names, no action is required.
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.
Path traversal (CWE-22) exists in cakephp/cakephp.
Check the vendor advisory for the affected versions of cakephp/cakephp.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.5.11.
Workaround: If developers are not using user-supplied data in element names, no action is required.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'cakephp/cakephp' . 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 'cakephp/cakephp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
cakephp/cakephpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
If developers are not using user-supplied data in element names, no action is required.パッチが適用されるまでの応急処置として、If developers are not using user-supplied data in element names, no action is required. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade cakephp/cakephp to 4.5.11ステージング環境で 4.5.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-48820 cakephp
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com