dbcve.org
Forgot PasswordApplication · Mendix

CVE-2023-27464

MEDIUM · 5.3 CVSS v3.1 Published 2023-04-11
Fix available
A fix is available. Upgrade to 3.7.1 / 4.1.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Forgot Password (Mendix 7 compatible) (All versions < V3.7.1), Mendix Forgot Password (Mendix 8 compatible) (All versions < V4.1.1), Mendix Forgot Password (Mendix 9 compatible) (All versions < V5.1.1). The affected versions of the module contain an observable response discrepancy issue that could allow an attacker to retrieve sensitive information.

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

The Mendix Forgot Password module has an observable response discrepancy vulnerability where the application returns different responses depending on whether a provided email address or username exists in the system. This allows attackers to enumerate valid user accounts by submitting various email addresses and analyzing the differing responses.

MitigationUpgrade the Mendix Forgot Password module to version V3.7.1 (Mendix 7), V4.1.1 (Mendix 8), or V5.1.1 (Mendix 9) or later to patch the vulnerability.

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
Forgot PasswordApplication
Affected:< 3.7.1>= 4.0.0, < 4.1.1>= 5.0.0, < 5.1.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Forgot Password module is in use
    Review the Mendix application modules or check the deployed application for a password reset/forgot password functionality accessible from the login page
    Affected if The Forgot Password module or similar password recovery feature is present and accessible
  2. Identify Forgot Password module version
    Open the Mendix project in Mendix Studio Pro, locate the Forgot Password module in the Project Explorer, and check the module version in the module details or the Marketplace download metadata; alternatively, check the application's deployment metadata if accessible
    Affected if The installed version is < 3.7.1 OR >= 4.0.0 and < 4.1.1 OR >= 5.0.0 and < 5.1.1
  3. Test for user enumeration vulnerability
    Submit two requests to the Forgot Password endpoint: one with a known-valid email/username and one with a random non-existent email/username. Compare the HTTP response codes, response times, and message content between the two requests
    Affected if The responses differ in a way that reveals whether the submitted email/username exists in the system (e.g., one returns 'email not found' while the other returns 'password reset email sent' or similar)

A user is affected if the Forgot Password module is deployed and the installed version falls within the vulnerable version ranges, or if the password reset endpoint reveals account existence through differing responses to valid versus invalid email submissions.

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 3.7.1 / 4.1.1 / 5.1.1 or later
Fixed in 3.7.14.1.15.1.1
Interim mitigation

Upgrade the Mendix Forgot Password module to version V3.7.1 (Mendix 7), V4.1.1 (Mendix 8), or V5.1.1 (Mendix 9) or later to patch the vulnerability.

Recommended fix High confidence

Forgot Password V3.7.1 (Mendix 7), V4.1.1 (Mendix 8), or V5.1.1 (Mendix 9) depending on your Mendix version

  1. 1. Identify the Mendix version your application is running (7, 8, or 9)
  2. 2. Download the Mendix Forgot Password module from the Mendix App Store or your organization's artifact repository
  3. 3. For Mendix 7 applications: Upgrade to Forgot Password version 3.7.1
  4. 4. For Mendix 8 applications: Upgrade to Forgot Password version 4.1.1
  5. 5. For Mendix 9 applications: Upgrade to Forgot Password version 5.1.1
  6. 6. Import the new module version into your Mendix Studio Pro project
  7. 7. Redeploy the application to apply the changes
  8. 8. Verify the password reset functionality works correctly after the upgrade
Caveat Review release notes for any behavior changes in the new module version before upgrading in production

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

Fix this in Forgot Password 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 the upgrade done

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-2023-27464 — 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-2023-27464 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