# CVE-2023-22727: Database Query::offset() and limit() vulnerable to SQL injection in cakephp

> Attackers can execute arbitrary SQL commands via unsanitized input in CakePHP's limit and offset methods, risking data exposure or modification.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jan 2023
- **Updated:** 10 Mar 2025
- **Also known as:** GHSA-6g8q-qfpv-57wp, UBUNTU-CVE-2023-22727

## What is CVE-2023-22727?

CVE-2023-22727 is a critical SQL injection vulnerability in cakephp, published on 17 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CakePHP is a development framework for PHP web apps. In affected versions the `Cake\Database\Query::limit()` and `Cake\Database\Query::offset()` methods are vulnerable to SQL injection if passed un-sanitized user request data. This issue has been fixed in 4.2.12, 4.3.11, 4.4.10. Users are advised to upgrade. Users unable to upgrade may mitigate this issue by using CakePHP's Pagination library. Manually validating or casting parameters to these methods will also mitigate the issue.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2023-22727?

12 open source packages ship an affected version, including cakephp/cakephp and cakephp/database. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cakephp/cakephp` | Packagist | From 4.2.0 | 4.2.12 |
| `cakephp/cakephp` | Packagist | From 4.2.0 | 4.2.12 |
| `cakephp/cakephp` | Packagist | From 4.3.0 | 4.3.11 |
| `cakephp/cakephp` | Packagist | From 4.3.0 | 4.3.11 |
| `cakephp/cakephp` | Packagist | From 4.4.0 | 4.4.10 |
| `cakephp/cakephp` | Packagist | From 4.4.0 | 4.4.10 |
| `cakephp/database` | Packagist | From 4.2.0 | 4.2.12 |
| `cakephp/database` | Packagist | From 4.2.0 | 4.2.12 |
| `cakephp/database` | Packagist | From 4.3.0 | 4.3.11 |
| `cakephp/database` | Packagist | From 4.3.0 | 4.3.11 |
| `cakephp/database` | Packagist | From 4.4.0 | 4.4.10 |
| `cakephp/database` | Packagist | From 4.4.0 | 4.4.10 |

Products: Cakephp Cakephp.

## How do I fix CVE-2023-22727?

Upgrade cakephp/cakephp to a fixed version for your release line: 4.2.12, 4.3.11 or 4.4.10.

## Is CVE-2023-22727 being exploited?

There is no known exploitation of CVE-2023-22727 in the wild and no public exploit code.

## Other vulnerabilities in cakephp

- [CVE-2020-35239](https://insights.sbomify.com/CVE-2020-35239/): CakePHP allows method override parameters to bypass CSRF checks (high 8.8)
- [CVE-2015-8379](https://insights.sbomify.com/CVE-2015-8379/): CakePHP might allow remote attackers to bypass CSRF protection mechanism via the _method parameter (high 8.8)
- [CVE-2019-11458](https://insights.sbomify.com/CVE-2019-11458/): Unsafe deserialization in SmtpTransport in CakePHP (high 7.5)
- [CVE-2016-4793](https://insights.sbomify.com/CVE-2016-4793/): CakePHP allows remote attackers to spoof their IP (high 7.5)
- [CVE-2026-23643](https://insights.sbomify.com/CVE-2026-23643/): CakePHP PaginatorHelper::limitControl() vulnerable to reflected cross-site-scripting (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-22727 and fix it if it is affected.

What it is: CVE-2023-22727 is a critical SQL injection vulnerability in cakephp, published on 17 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-22727 in the wild and no public exploit code.

Affected packages and fixed versions:
- cakephp/cakephp (Packagist): affected from 4.2.0; fixed in 4.2.12
- cakephp/cakephp (Packagist): affected from 4.2.0; fixed in 4.2.12
- cakephp/cakephp (Packagist): affected from 4.3.0; fixed in 4.3.11
- cakephp/cakephp (Packagist): affected from 4.3.0; fixed in 4.3.11
- cakephp/cakephp (Packagist): affected from 4.4.0; fixed in 4.4.10
- cakephp/cakephp (Packagist): affected from 4.4.0; fixed in 4.4.10
- cakephp/database (Packagist): affected from 4.2.0; fixed in 4.2.12
- cakephp/database (Packagist): affected from 4.2.0; fixed in 4.2.12
- cakephp/database (Packagist): affected from 4.3.0; fixed in 4.3.11
- cakephp/database (Packagist): affected from 4.3.0; fixed in 4.3.11
- cakephp/database (Packagist): affected from 4.4.0; fixed in 4.4.10
- cakephp/database (Packagist): affected from 4.4.0; fixed in 4.4.10

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-22727/ (Markdown: https://insights.sbomify.com/CVE-2023-22727/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-22727
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-22727
- OSV: https://osv.dev/vulnerability/CVE-2023-22727

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-22727/
Summaries are generated and may contain mistakes; the official description above is the record.