CVE-2023-25957
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 SAML (Mendix 7 compatible) (All versions >= V1.16.4 < V1.17.3), Mendix SAML (Mendix 8 compatible) (All versions >= V2.2.0 < V2.3.0), Mendix SAML (Mendix 9 latest compatible, New Track) (All versions >= V3.1.9 < V3.3.1), Mendix SAML (Mendix 9 latest compatible, Upgrade Track) (All versions >= V3.1.8 < V3.3.0), Mendix SAML (Mendix 9.6 compatible, New Track) (All versions >= V3.1.9 < V3.2.7), Mendix SAML (Mendix 9.6 compatible, Upgrade Track) (All versions >= V3.1.8 < V3.2.6). The affected versions of the module insufficiently verify the SAML assertions. This could allow unauthenticated remote attackers to bypass authentication and get access to the application. For compatibility reasons, fix versions still contain this issue, but only when the recommended, default configuration option `'Use Encryption'` is disabled.
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 confidenceThe Mendix SAML module has insufficient verification of SAML assertions, allowing unauthenticated attackers to forge SAML responses and bypass authentication. This affects multiple tracked versions for Mendix 7, 8, and 9. The vulnerability persists in patched versions unless the 'Use Encryption' option is enabled.
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>= 1.16.4, < 1.17.2>= 2.2.0, < 2.2.3>= 3.1.9, < 3.2.5CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Locate the Mendix SAML module in your projectOpen your Mendix project in Studio Pro and look for the 'SAML' module in the Project Explorer under 'App Modules', or check your project's 'userlib' folder for the SAML module JAR fileAffected if The SAML module is not present in your project
-
Identify the installed SAML module versionRight-click the SAML module in Project Explorer and select 'Show module version', or inspect the JAR file name in userlib (e.g., saml-1.16.4.jar) which contains the version numberAffected if The version falls within any of these ranges: >= 1.16.4 and < 1.17.2, OR >= 2.2.0 and < 2.2.3, OR >= 3.1.9 and < 3.2.5
-
Verify the 'Use Encryption' configuration settingIn Mendix Studio Pro, open the SAML module and navigate to 'Settings' or 'Configuration' > look for the 'Use Encryption' checkbox or toggle. Alternatively, check your project's 'settings-native.xml' or 'settings-web.xml' files for the SAML configuration sectionAffected if The 'Use Encryption' option is disabled or not explicitly set to true
You are affected if the SAML module version is within any of the affected version ranges AND the 'Use Encryption' option is disabled in the module configuration, regardless of whether you have applied a patch version.
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 · scoped1.17.22.2.33.2.5
Upgrade to the fixed versions (V1.17.3, V2.3.0, V3.3.1, V3.3.0, V3.2.7, or V3.2.6 depending on track) AND ensure the 'Use Encryption' configuration option is enabled in the SAML module settings.
Mendix SAML module V1.17.3 (Mendix 7), V2.3.0 (Mendix 8), V3.3.1 (Mendix 9 New Track), V3.3.0 (Mendix 9 Upgrade Track), V3.2.7 (Mendix 9.6 New Track), or V3.2.6 (Mendix 9.6 Upgrade Track) - depending on your compatibility track
- 1. Identify the Mendix SAML module version currently in use from the Mendix Studio Pro project or deployment manifest.
- 2. Determine which Mendix compatibility track applies (Mendix 7, 8, or 9, and for Mendix 9: New Track, Upgrade Track, or 9.6 compatible).
- 3. Upgrade the Mendix SAML module to the fixed version for your track: For Mendix 7 compatible: upgrade to V1.17.3 or later; For Mendix 8 compatible: upgrade to V2.3.0 or later; For Mendix 9 latest compatible (New Track): upgrade to V3.3.1 or later; For Mendix 9 latest compatible (Upgrade Track): upgrade to V3.3.0 or later; For Mendix 9.6 compatible (New Track): upgrade to V3.2.7 or later; For Men
- 4. In the Mendix SAML module configuration, verify that the 'Use Encryption' setting is enabled (this is the recommended default).
- 5. Redeploy the application with the updated module.
- 6. Test SAML authentication flows to verify the fix is working correctly.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25957 — 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-25957 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