CVE-2023-45794
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 · uneditedA vulnerability has been identified in Mendix Applications using Mendix 10 (All versions < V10.4.0), Mendix Applications using Mendix 7 (All versions < V7.23.37), Mendix Applications using Mendix 8 (All versions < V8.18.27), Mendix Applications using Mendix 9 (All versions < V9.24.10). A capture-replay flaw in the platform could have an impact to apps built with the platform, if certain preconditions are met that depend on the app's model and access control design. This could allow authenticated attackers to access or modify objects without proper authorization, or escalate privileges in the context of the vulnerable app.
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 confidenceCapture-replay vulnerability in Mendix platform allows authenticated attackers to bypass authorization controls and access or modify objects without proper permissions, or escalate privileges, depending on the application's model and access control design.
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>= 7.0.0, < 7.23.37>= 8.0.0, < 8.18.27>= 9.0.0, < 9.24.10>= 10.0.0, < 10.4.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Mendix runtime versionCheck the Mendix runtime version by reviewing the application deployment manifest, model metadata, or the runtime's /rest/_mxversion/ endpoint if exposed. In deployment, review the 'm2ee.yaml' or equivalent configuration file that specifies the Mendix version.Affected if The running Mendix runtime version falls within any of these ranges: 7.0.0 to 7.23.36, 8.0.0 to 8.18.26, 9.0.0 to 9.24.09, or 10.0.0 to 10.3.x.
-
Determine if Entity Access Rules are in useReview the Mendix Domain Model for configured Entity Access Rules. In Studio Pro, open each entity and inspect the 'Access Rules' tab. In a deployed app, review the metadata exported from the model or the entity configuration in the runtime database.Affected if Entity Access Rules are defined but the application relies solely on them for authorization without additional custom microflow or Java-based access control layers.
-
Identify custom Java actions that handle authorizationScan the application's Java custom code for any actions that implement permission checks, bypass Mendix's built-in access control, or handle object create/read/write/delete operations. Review the project's 'javasource' folder for classes extending Core or IMendixObject.Affected if Custom Java actions exist that perform authorization checks or object access without invoking Mendix's built-in access control, and the application is running on an affected version.
-
Review microflow-based access control patternsExamine microflows used for authorization, particularly those called before CRUD operations or those enforcing row-level security. Look for microflows that override default access or implement custom permission logic.Affected if The application uses microflows to enforce access control that could be bypassed through the capture-replay vulnerability in the affected versions.
A user is affected if their Mendix runtime version is within any of the four vulnerable ranges AND the application uses Mendix's built-in Entity Access Rules, custom Java authorization, or microflow-based access control that could be bypassed via capture-replay.
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.
dbcve · scoped7.23.378.18.279.24.10
Upgrade Mendix runtime to version V10.4.0, V7.23.37, V8.18.27, or V9.24.10 or later as appropriate for the version line in use.
Upgrade to Mendix 7.23.37, 8.18.27, 9.24.10, or 10.4.0 (or later) depending on your current major version branch
- 1. Backup your Mendix application project and database before upgrading
- 2. Review the Mendix release notes for your target version (7.23.37, 8.18.27, 9.24.10, or 10.4.0 depending on your current major version) for any breaking changes
- 3. Test the upgrade in a staging or development environment first
- 4. Update your Mendix Studio Pro orMx Azure deployment to the fixed version
- 5. Verify that your application's access control rules and authentication flow work correctly after the upgrade
- 6. Deploy the updated application to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45794 — 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-2023-45794 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