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

SQL Injection in cakephp/database (CVE-2026-79752)

Summary

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

Original description

The description as published by the source.

Impact

The FunctionsBuilder::cast($field, $dataType), extract($part, $expr), datePart($part, $expr), dateAdd($expr, $value, $unit) methods are vulnerable to SQL injection if user controlled data is supplied to the ($dataType / $part / $unit) parameters.

Patches

5.3.7, 5.2.14, 5.1.9, 4.6.5, 4.5.12 contain fixes

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

CVE-2026-79752 (cakephp/database) — CWE-89
Patched: 5.3.7 — 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/database.

📍 Affected scope

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

🔥 Severity

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

🔧 How to fix

Update to 5.3.7.

🛡️ 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/database' . 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/database' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で cakephp/database を 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/database to 5.3.7

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

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

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

Affected packages

composer cakephp/database
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.5.12"}]}]
composer cakephp/cakephp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.7"}]}]

References

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