CVE-2023-32692

Workarounds

Setting validation rules with an array.

E.g.:

$validation->setRules([
    'email' => ['required', 'valid_email, 'is_unique[users.email,id,{id}]'],
]);

References

• https://codeigniter4.github.io/userguide/libraries/validation.html#validation-placeholders
• https://codeigniter4.github.io/userguide/incoming/controllers.html#validating-data
• https://codeigniter4.github.io/userguide/models/model.html#in-model-validation

For more information

If you have any questions or comments about this advisory:

• Open an issue in codeigniter4/CodeIgniter4
• Email us at SECURITY.md

This vulnerability allows attackers to execute arbitrary code when you use Validation Placeholders.

The vulnerability exists in the Validation library, and validation methods in the controller and in-model validation are also vulnerable because they use the Validation library internally.

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2023-32692 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.3.5); upgrading removes the vulnerable code path.

Kodem intelligence

Upgrade to v4.3.5 or later.

1. What is CVE-2023-32692? CVE-2023-32692 is a critical-severity code injection vulnerability in codeigniter4/framework (composer), affecting versions < 4.3.5. It is fixed in 4.3.5. Untrusted input is evaluated as executable code within the application's runtime environment.
2. How severe is CVE-2023-32692? CVE-2023-32692 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of codeigniter4/framework are affected by CVE-2023-32692? codeigniter4/framework (composer) versions < 4.3.5 is affected.
4. Is there a fix for CVE-2023-32692? Yes. CVE-2023-32692 is fixed in 4.3.5. Upgrade to this version or later.
5. Is CVE-2023-32692 exploitable, and should I be worried? Whether CVE-2023-32692 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-32692 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-32692? Upgrade codeigniter4/framework to 4.3.5 or later.