Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-77635 – SQL Injection – CakePHP 5.1.0–5.1.9, 5.2.0–5.2.14, 5.3.0–5.3.6

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-77635 is a SQL injection vulnerability (CWE-89) in the CakePHP framework’s PostgreSQL database driver, specifically in the FunctionsBuilder::jsonValue($field, $jsonPath) method. When an application passes user-controlled data into the $jsonPath parameter, an attacker can inject arbitrary SQL, leading to potential data disclosure and manipulation. The issue carries a critical CVSS score of 9.2 and affects multiple 5.x release lines of CakePHP.

Technical details

  • Root cause: FunctionsBuilder::jsonValue() builds a SQL fragment for JSON path queries against PostgreSQL without properly neutralizing special characters in the $jsonPath argument.
  • Trigger condition: An application must pass user-supplied (attacker-controlled) input directly into the $jsonPath parameter of jsonValue() when using CakePHP’s PostgreSQL driver.
  • Attack vector: Network — exploitation occurs through normal application requests that reach vulnerable query-building code, requiring no authentication or user interaction.
  • Impact: High confidentiality and integrity impact (unauthorized read/modification of database contents) with low availability impact, consistent with a SQL injection allowing attacker-controlled queries to execute against the backend PostgreSQL database.

Affected software

  • cakephp/cakephp: 5.1.0 – 5.1.9
  • cakephp/cakephp: 5.2.0 – 5.2.14
  • cakephp/cakephp: 5.3.0 – 5.3.6
  • cakephp/database: 5.1.0 – 5.1.9
  • cakephp/database: 5.2.0 – 5.2.14
  • cakephp/database: 5.3.0 – 5.3.6

Severity

  • CVSS v4.0 Base Score: 9.2 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade to the patched releases — CakePHP 5.1.10, 5.2.15, or 5.3.7, depending on the branch in use.
  • If patching is not immediately possible: Do not pass user-controlled data into FunctionsBuilder::jsonValue() or its $jsonPath parameter; validate/sanitize any input that reaches this function, and review application code for other call sites that forward request data into PostgreSQL JSON path queries.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Meta tag application-name: CakePHP

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge