dbcve.org
CodeigniterApplication

CVE-2022-24712

HIGH · 8.8 CVSS v3.1 Published 2022-02-28
Fix available
A fix is available. Upgrade to 4.1.9 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
CodeIgniter4 is the 4.x branch of CodeIgniter, a PHP full-stack web framework. A vulnerability in versions prior to 4.1.9 might allow remote attackers to bypass the CodeIgniter4 Cross-Site Request Forgery (CSRF) protection mechanism. Users should upgrade to version 4.1.9. There are workarounds for this vulnerability, but users will still need to code as these after upgrading to v4.1.9. Otherwise, the CSRF protection may be bypassed. If auto-routing is enabled, check the request method in the controller method before processing. If auto-routing is disabled, either avoid using `$routes->add()` and instead use HTTP verbs in routes; or check the request method in the controller method before processing.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

CodeIgniter4 versions prior to 4.1.9 have a CSRF protection bypass vulnerability where attackers can circumvent the framework's CSRF token validation, allowing unauthorized cross-site request forgery attacks on state-changing operations.

MitigationUpgrade to CodeIgniter4 4.1.9 or later and implement request method validation (checking HTTP verbs) in controller methods before processing any state-changing actions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CodeigniterApplication
Affected:>= 4.0.0, < 4.1.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify CodeIgniter4 version
    Check the version file at system/CodeIgniter.php (look for the $version variable) or in composer.json
    Affected if version is 4.0.0 or higher but lower than 4.1.9
  2. Confirm CSRF protection is in use
    Inspect app/Config/Filters.php and verify that 'csrf' is present in the $filters array (either global or per-route)
    Affected if CSRF filter is configured but framework version is vulnerable
  3. Check CSRF token validation logic
    Examine system/Security/Security.php - look for the verifyCSRFToken() or similar method handling token validation
    Affected if The CSRF token validation code is from a version prior to 4.1.9 (vulnerable implementation)
  4. Verify state-changing endpoints exist
    Review application controllers for methods performing database writes, file operations, or configuration changes (POST, PUT, DELETE handlers)
    Affected if State-changing endpoints exist and CSRF protection can be bypassed due to vulnerable version

Environment is affected if CodeIgniter4 version is 4.0.0 through 4.1.8 and CSRF protection is configured for state-changing routes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.1.9 or later
Fixed in 4.1.9
Interim mitigation

Upgrade to CodeIgniter4 4.1.9 or later and implement request method validation (checking HTTP verbs) in controller methods before processing any state-changing actions.

Recommended fix High confidence

CodeIgniter 4.1.9

  1. Upgrade CodeIgniter from any version < 4.1.9 to version 4.1.9 or later (e.g., `composer require codeigniter4/framework:^4.1.9` or update composer.json)
  2. If using auto-routing (enabled by default), add request method validation in each controller method before processing: check `$this->request->getMethod() === 'post'` (or appropriate method) before any state-changing operation
  3. If using defined routes, replace `$routes->add()` with HTTP verb-based routes like `$routes->post()` to ensure only valid HTTP methods are accepted
  4. After upgrading, verify CSRF tokens are being properly validated by testing form submissions
  5. Review application logs to confirm no CSRF validation errors occur during normal operations
Caveat Review the CodeIgniter 4.1.9 changelog for any breaking changes from your current version; the workaround requirements (adding method checks in controllers) may require code changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Codeigniter Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24712 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24712 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data