dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-42550

HIGH · 8.8 CVSS v3.1 Published 2026-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Flight is an extensible micro-framework for PHP. Prior to 3.18.1, SimplePdo::insert(), SimplePdo::update(), and SimplePdo::delete() build SQL statements by concatenating the $table argument and the keys of the $data array directly into the query, with no identifier quoting and no validation. When an application forwards user-controlled data shapes to these helpers — a common and documented pattern, e.g. $db->insert('users', $request->data->getData()) — an attacker can inject arbitrary SQL by crafting malicious array keys. This vulnerability is fixed in 3.18.1.

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

SQL injection vulnerability in Flight PHP framework's SimplePdo class where insert(), update(), and delete() methods concatenate user-controlled array keys directly into SQL queries without identifier quoting or parameterization, allowing arbitrary SQL injection via crafted array keys.

MitigationUpgrade to Flight framework version 3.18.1 or later which implements proper identifier quoting; alternatively, validate and sanitize all array keys before passing them to these database methods.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 Flight framework version
    Check your composer.json file for the 'flightphp/core' package version, or run 'composer show flightphp/core' to see the installed version
    Affected if version is lower than 3.18.1 and the SimplePdo class is in use
  2. Locate SimplePdo class usage
    Search your codebase for 'use flight\database\SimplePdo' or 'new SimplePdo' to determine if this class is being used
    Affected if SimplePdo class is instantiated in your application
  3. Identify insert/update/delete method calls
    Search for method calls like $db->insert(), $db->update(), or $db->delete() in your codebase, particularly where arrays are passed as parameters
    Affected if these methods are called with arrays containing keys derived from user input
  4. Verify array key source
    Examine the arrays passed to insert(), update(), and delete() methods and trace whether their keys come from $_GET, $_POST, $_REQUEST, or other user-controlled sources
    Affected if array keys originate from user input without sanitization
  5. Check for proper parameterization
    Review the SimplePdo class implementation in vendor/flightphp/core/src/database/SimplePdo.php to see if identifier quoting is applied to array keys in these methods
    Affected if the code directly concatenates array keys into SQL without using placeholder parameterization or proper identifier quoting

You are affected if you use Flight framework versions prior to 3.18.1 and your application passes user-controlled array keys to the SimplePdo class insert(), update(), or delete() methods without sanitization.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Flight framework version 3.18.1 or later which implements proper identifier quoting; alternatively, validate and sanitize all array keys before passing them to these database methods.

Recommended fix High confidence

3.18.1

  1. Identify the current version of Flight PHP framework in use by checking composer.json or composer.lock
  2. Run 'composer require flightphp/core:^3.18.1' or 'composer update flightphp/core' to upgrade to the fixed version
  3. Verify the upgrade was successful by checking the installed version with 'composer show flightphp/core'
  4. Test application functionality, particularly database operations using insert(), update(), and delete() methods to confirm the fix works and no regressions were introduced
Caveat Minimal risk - this is a patch release fixing a security vulnerability; however, always test in staging first

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42550 — 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-2026-42550 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