dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-40592

MEDIUM · 6.1 CVSS v3.1 Published 2025-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Studio Pro 10 (All versions < V10.23.0), Mendix Studio Pro 10.12 (All versions < V10.12.17), Mendix Studio Pro 10.18 (All versions < V10.18.7), Mendix Studio Pro 10.6 (All versions < V10.6.24), Mendix Studio Pro 11 (All versions < V11.0.0), Mendix Studio Pro 8 (All versions < V8.18.35), Mendix Studio Pro 9 (All versions < V9.24.35). A zip path traversal vulnerability exists in the module installation process of Studio Pro. By crafting a malicious module and distributing it via (for example) the Mendix Marketplace, an attacker could write or modify arbitrary files in directories outside a developer’s project directory upon module installation.

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

A zip path traversal vulnerability exists in Mendix Studio Pro's module installation process. By crafting a malicious module with path traversal sequences (e.g., ../../) embedded in zip file entries, an attacker can write or modify arbitrary files outside the developer's intended project directory when the module is installed. This allows file write/modify access to locations on the filesystem that should be restricted.

MitigationUpgrade Mendix Studio Pro to one of the patched versions: V10.23.0, V10.12.17, V10.18.7, V10.6.24, V11.0.0, V8.18.35, or V9.24.35. Exercise caution when installing modules from untrusted sources such as the Mendix Marketplace until upgraded.

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
High
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/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. Verify Mendix Studio Pro installation
    Check for Mendix Studio Pro installation directory, typically at C:\Program Files\Mendix\ or look for Mendix Studio Pro in the Windows Start Menu
    Affected if Mendix Studio Pro is installed on the system
  2. Determine installed version
    Open Mendix Studio Pro, go to Help > About, or check the version file in the installation directory (version.txt or similar)
    Affected if The installed version is lower than the patched versions (V10.23.0, V10.12.17, V10.18.7, V10.6.24, V11.0.0, V8.18.35, V9.24.35) and thus unpatched
  3. Confirm module installation feature usage
    Check if the user has imported or installed any modules into their Mendix projects, particularly from external sources
    Affected if Modules have been installed in any Mendix project using the module import feature
  4. Assess module source trust
    Review the source of installed modules - determine if any were obtained from third-party sources outside the official Mendix Marketplace or from untrusted developers
    Affected if Modules from untrusted or unknown sources have been installed
  5. Inspect project directory structure
    Check the project's local directory for any unexpected files or directories that appear outside the intended project folder structure, which could indicate prior exploitation
    Affected if Unexpected files or directories exist outside the project folder that were not intentionally created

The user is affected if Mendix Studio Pro is installed with an unpatched version (below the fixed releases) and modules have been installed, especially from untrusted sources.

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 Mendix Studio Pro to one of the patched versions: V10.23.0, V10.12.17, V10.18.7, V10.6.24, V11.0.0, V8.18.35, or V9.24.35. Exercise caution when installing modules from untrusted sources such as the Mendix Marketplace until upgraded.

Recommended fix High confidence

V10.23.0 (10.x), V10.12.17 (10.12.x), V10.18.7 (10.18.x), V10.6.24 (10.6.x), V11.0.0 (11.x), V8.18.35 (8.x), V9.24.35 (9.x)

  1. Identify the current installed version of Mendix Studio Pro by checking Help > About in the application
  2. Determine which major version line (8, 9, 10, or 11) your installation belongs to
  3. For Mendix Studio Pro 8: upgrade to version V8.18.35 or higher
  4. For Mendix Studio Pro 9: upgrade to version V9.24.35 or higher
  5. For Mendix Studio Pro 10.6.x: upgrade to version V10.6.24 or higher
  6. For Mendix Studio Pro 10.12.x: upgrade to version V10.12.17 or higher
  7. For Mendix Studio Pro 10.18.x: upgrade to version V10.18.7 or higher
  8. For Mendix Studio Pro 10.x (latest): upgrade to version V10.23.0 or higher
Caveat Upgrading between major version lines (e.g., 8 to 9, 10 to 11) may require project migration and compatibility testing; review Mendix migration guides before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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