CVE-2025-2140 json
IBM Engineering Requirements Management Doors Next spoofing
published last yr. modified last mo. also EUVD-2025-33896
- cvss
- 5.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- ibm.com/support/pages/node/7247716 advisory
Is CVE-2025-2140 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa vex VA-25-297-01 updated cvss 5.4
IBM DOORS Next Generation multiple vulnerabilities
-
IBM Engineering Requirements Management DOORS Next >=7.0.2, <7.0.2 iFix036, >=7.0.3, <7.0.3 iFix019, >=7.1, <7.1.0 iFix005affected: vendor fix ibm.com
-
IBM Engineering Requirements Management DOORS Next 7.0.2 iFix036, 7.0.3 iFix019, 7.1.0 iFix005fixed: vendor fix ibm.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.7 | CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected products
- IBM Engineering Requirements Management Doors Next
Classification
- Weakness
-
- CWE-346 Origin Validation Error
References
-
ibm.com
/support/pages/node/7247716
vendor-advisory, patch
Sources
- CVE List CVE-2025-2140
- NVD CVE-2025-2140
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.