dbcve.org
Engineering Requirements Management Doors NextApplication · Ibm

CVE-2025-2140

MEDIUM · 5.7 CVSS v3.1 Published 2025-10-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
IBM Engineering Requirements Management Doors Next 7.0.2, 7.0.3, and 7.1 could allow an authenticated user on the network to spoof email identity of the sender due to improper verification of source 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 · moderate confidence

IBM Engineering Requirements Management Doors Next versions 7.0.2, 7.0.3, and 7.1 contains a vulnerability allowing authenticated network users to spoof the email identity of the sender due to improper verification of source data in the email subsystem.

MitigationImplement proper verification of email source data, likely including validation of sender identity, authentication checks, and possibly integration with standard email authentication protocols (SPF, DKIM, DMARC) or application-level sender verification.

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
Engineering Requirements Management Doors NextApplication
Affected:= 7.0.2= 7.0.3= 7.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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/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. Identify installed Doors Next version
    Access the Doors Next administration console or check the product 'About' information to determine the exact version number
    Affected if Version is 7.0.2, 7.0.3, or 7.1
  2. Confirm email subsystem is configured
    Check if email notifications or outbound email features are enabled in the Doors Next administration settings
    Affected if Email subsystem is active and configured for the product
  3. Review email sender configuration
    Examine the email configuration settings in the Doors Next admin console for any sender verification or authentication controls
    Affected if Sender verification is absent, disabled, or set to allow arbitrary sender addresses
  4. Inspect email relay settings
    Look at the email server relay configuration within Doors Next to see if external sender addresses can be specified
    Affected if The email relay permits spoofed sender identities without validation
  5. Check email authentication protocols
    Review whether SPF, DKIM, or DMARC validation is enforced for outgoing emails originating from Doors Next
    Affected if No email authentication protocols are enforced for sender verification

You are affected if you run Doors Next version 7.0.2, 7.0.3, or 7.1 with the email subsystem enabled and without proper sender identity verification configured.

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

Implement proper verification of email source data, likely including validation of sender identity, authentication checks, and possibly integration with standard email authentication protocols (SPF, DKIM, DMARC) or application-level sender verification.

Recommended fix Moderate confidence

Latest available 7.x release or IBM-provided security patch for your current version (contact IBM Support for specific fix version)

  1. Identify your current IBM Engineering Requirements Management Doors Next version (7.0.2, 7.0.3, or 7.1) from the IBM Jazz-based server administration console
  2. Contact IBM Support or access the IBM Fix Central portal to obtain the security fix for CVE-2025-2140
  3. Request the interim fix (iFix) or upgrade package specific to your current version
  4. Apply the fix following IBM's standard patching procedure for Doors Next requirements management
  5. Verify the fix was applied successfully by checking the version information and testing email functionality
  6. Confirm the CORS/origin validation is working correctly by testing from authorized network locations
Caveat Review IBM's fix documentation for any configuration changes required after applying the security patch

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

Fix this in Engineering Requirements Management Doors Next Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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