dbcve.org
MendixApplication

CVE-2022-24309

HIGH · 8.1 CVSS v3.1 Published 2022-03-08
Fix available
A fix is available. Upgrade to 7.23.29 / 8.18.16 or later.
See remediation →
87/100
Remediation priority · High
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
A vulnerability has been identified in Mendix Runtime V7 (All versions < V7.23.29), Mendix Runtime V8 (All versions < V8.18.16), Mendix Runtime V9 (All versions < V9.13 only with Runtime Custom Setting *DataStorage.UseNewQueryHandler* set to False). If an entity has an association readable by the user, then in some cases, Mendix Runtime may not apply checks for XPath constraints that parse said associations, within apps running on affected versions. A malicious user could use this to dump and manipulate sensitive data.

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

Mendix Runtime fails to enforce XPath constraints on associations that are readable by users, allowing authorization bypass. The vulnerability exists in V7 (<7.23.29), V8 (<8.18.16), and V9 (<9.13) when the DataStorage.UseNewQueryHandler setting is False. Attackers can read or manipulate data through associations that should be protected by XPath constraints.

MitigationUpgrade Mendix Runtime to V7.23.29+, V8.18.16+, or V9.13+ respectively. For V9, alternatively enable the DataStorage.UseNewQueryHandler setting to True as a mitigation before upgrading.

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
MendixApplication
Affected:< 7.23.29>= 8.0.0, < 8.18.16>= 9.0.0, < 9.13

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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Identify the Mendix Runtime version
    Locate the Mendix Runtime version in your deployment configuration, about page, or deployment metadata. This is typically found in the project settings, deployment package, or runtime environment information.
    Affected if The installed version is < 7.23.29 for V7, or >= 8.0.0 and < 8.18.16 for V8, or >= 9.0.0 and < 9.13 for V9.
  2. Check the DataStorage.UseNewQueryHandler setting
    Inspect your Mendix configuration files (such as custom settings in the deployment modeler, environment variables, or configuration files) for the DataStorage.UseNewQueryHandler setting.
    Affected if The DataStorage.UseNewQueryHandler setting is set to False or is not explicitly set to True (the default behavior before the fix uses False).

You are affected if your Mendix Runtime version falls within the vulnerable ranges AND the DataStorage.UseNewQueryHandler setting is False or not explicitly set to True.

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 7.23.29 / 8.18.16 / 9.13 or later
Fixed in 7.23.298.18.169.13
Interim mitigation

Upgrade Mendix Runtime to V7.23.29+, V8.18.16+, or V9.13+ respectively. For V9, alternatively enable the DataStorage.UseNewQueryHandler setting to True as a mitigation before upgrading.

Recommended fix High confidence

Mendix V7: 7.23.29+ | Mendix V8: 8.18.16+ | Mendix V9: 9.13+

  1. 1. Identify the Mendix Runtime version currently deployed in your application
  2. 2. For Mendix V7.x applications: Upgrade to version 7.23.29 or later
  3. 3. For Mendix V8.x applications: Upgrade to version 8.18.16 or later
  4. 4. For Mendix V9.x applications: Upgrade to version 9.13 or later
  5. 5. If using Mendix V9 with DataStorage.UseNewQueryHandler=False, ensure the Runtime Custom Setting is removed or set to True after upgrading to V9.13 or later
  6. 6. Test the upgraded application thoroughly, especially access control and XPath-constrained data access
Caveat Mendix minor version upgrades may introduce breaking changes; review release notes and test thoroughly before production deployment

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

Fix this in Mendix Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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