Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-77635

SQL Injection in cakephp/cakephp (CVE-2026-77635)

Summary

SQL injection in cakephp/cakephp (CVE-2026-77635). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.1.10 or later.

Original description

The description as published by the source.

Impact

The FunctionsBuilder::jsonValue($field, $jsonPath) methods with the Postgres driver is vulnerable to SQL injection if user controlled data is supplied to the $jsonPath parameter.

Patches

5.1.10, 5.2.15, 5.3.7

Workarounds

Don't provide user controlled data to these functions/parameters.

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-77635 has been found in cakephp/cakephp.
Risk of unauthorized operations or information disclosure.
What to do: upgrade cakephp/cakephp to 5.1.10 or later.
If unsure, ask your IT team or search "cakephp/cakephp CVE-2026-77635" on the vendor's site.

CVE-2026-77635 (cakephp/cakephp) — CWE-89
Patched: 5.1.10 — apply immediately
Workaround: Don't provide user controlled data to these functions/parameters.
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

SQL injection (CWE-89) exists in cakephp/cakephp.

📍 Affected scope

Check the vendor advisory for the affected versions of cakephp/cakephp.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.1.10.

🛡️ Workaround

Workaround: Don't provide user controlled data to these functions/parameters.

🔍 Detection

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

  1. 1
    Identify exposure identify 
    grep -r 'cakephp/cakephp' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で cakephp/cakephp を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Don't provide user controlled data to these functions/parameters.

    パッチが適用されるまでの応急処置として、Don't provide user controlled data to these functions/parameters. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade cakephp/cakephp to 5.1.10

    ステージング環境で 5.1.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer cakephp/cakephp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.1.10"}]}]
composer cakephp/database
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.1.10"}]}]
Packagist cakephp/cakephp
[{"type":"ECOSYSTEM","events":[{"introduced":"5.1.0"},{"fixed":"5.1.10"}]}]
Packagist cakephp/database
[{"type":"ECOSYSTEM","events":[{"introduced":"5.1.0"},{"fixed":"5.1.10"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details