dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-42474

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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
SQL injection vulnerability in MixPHP Framework 2.x thru 2.2.17 via crafted `data` array to the data function in BuildHelper.php.

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 · moderate confidence

SQL injection vulnerability in MixPHP Framework 2.x (up to 2.2.17) allows attackers to inject malicious SQL queries through a crafted `data` array passed to the `data` function in BuildHelper.php. This occurs when user-controlled input is directly incorporated into SQL queries without proper parameterization.

MitigationUpgrade MixPHP Framework to a version beyond 2.2.17 that patches this vulnerability, or implement prepared statement parameter binding for all SQL queries in BuildHelper.php that handle the data array input.

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

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

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. Confirm MixPHP Framework is in use
    Check for MixPHP by looking for its vendor directory, composer.json with mixphp/framework dependency, or the presence of BuildHelper.php in your codebase
    Affected if MixPHP Framework 2.x is present in the application
  2. Check installed MixPHP version
    Review composer.json or composer.lock for the mixphp/framework version number; if using a standalone BuildHelper.php, check the file header comments for version info
    Affected if Version is 2.x up to and including 2.2.17 (any 2.0.x through 2.2.17 release)
  3. Locate BuildHelper.php in your application
    Search the codebase for BuildHelper.php, typically found in the helpers or src directory of the MixPHP installation
    Affected if BuildHelper.php exists and is part of the deployed application
  4. Identify usage of the data function
    Search code for calls to BuildHelper::data() or \mix\db\BuildHelper::data() where the data function is invoked; review any custom code that interacts with this helper
    Affected if The data function from BuildHelper.php is being called within the application
  5. Check if user input reaches the data function unsafely
    Audit the code paths that call the data function: trace whether $_GET, $_POST, $_REQUEST, or other user-controlled arrays are passed directly to the data parameter without prepared statement binding
    Affected if User-controlled input (from request parameters, form data, or API input) flows directly into the data function without parameterized queries

You are affected if MixPHP Framework 2.x version 2.2.17 or earlier is in use, BuildHelper.php with its data function is present, and user input is passed to that function without prepared statement parameter binding.

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 MixPHP Framework to a version beyond 2.2.17 that patches this vulnerability, or implement prepared statement parameter binding for all SQL queries in BuildHelper.php that handle the data array input.

Recommended fix Moderate confidence

MixPHP 2.2.18 or later (e.g., 2.2.18, 2.3.x)

  1. 1. Identify the current MixPHP version in your project (check composer.json or vendor/composer/installed.json).
  2. 2. Update the MixPHP framework requirement in composer.json to version 2.2.18 or later, for example: "mixphp/framework": "^2.2.18".
  3. 3. Run `composer update mixphp/framework` to fetch the fixed version.
  4. 4. Review the release notes for any configuration or behavioral changes that may affect your application.
  5. 5. Test your application thoroughly, especially the BuildHelper::data() function, to confirm the SQL injection is remediated.
  6. 6. Deploy the updated application to production.
Caveat Minor changes possible; review the release notes for any breaking changes before upgrading.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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