CVE-2026-42475
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 · uneditedSQL injection vulnerability in MixPHP Framework 2.x thru 2.2.17 via crafted `on` array to the joinOn 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 confidenceSQL injection vulnerability in MixPHP Framework allows remote attackers to inject malicious SQL queries through the 'on' array parameter to the joinOn function in BuildHelper.php, where unsanitized user input is directly incorporated into SQL queries.
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>= 2.0.1, <= 2.2.17CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify MixPHP Framework versionLocate the core MixPHP files (such as composer.json or a version.php file in the vendor or src directory) and read the declared version numberAffected if The installed version is between 2.0.1 and 2.2.17 inclusive
-
Locate BuildHelper.phpSearch the project for the file BuildHelper.php within the MixPHP source code structure, typically under src/ or vendor/mix/ directoriesAffected if The file exists and contains the joinOn function
-
Inspect joinOn function for unsanitized inputOpen BuildHelper.php and examine the joinOn method. Look for code that directly uses the 'on' parameter from user input in SQL query construction without using parameterized queries or input sanitizationAffected if The 'on' array parameter is concatenated directly into SQL without prepared statements or escaping functions
-
Check if joinOn is used with external inputSearch codebases that utilize MixPHP for calls to joinOn where the 'on' parameter receives values from $_GET, $_POST, or other user-controllable sourcesAffected if Applications pass user-supplied values to the joinOn 'on' parameter without validation
You are affected if you run MixPHP Framework versions 2.0.1 through 2.2.17 AND your application passes user-controlled input to the joinOn function's 'on' parameter without sanitization.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate MixPHP Framework to version 2.2.18 or later to receive the official patch, or implement proper input sanitization and parameterized queries in the joinOn function to prevent SQL injection.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42475 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-42475 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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