Authenticated comment deletion via client-side authorization
Published Oct 12, 2025 · Updated Oct 14, 2025
Broken access control in IBM DOORS Next 7.0.2, 7.0.3, and 7.1 allows remote authenticated users to delete comments owned by others. The comment-deletion workflow relies on client-side enforcement instead of applying the ownership authorization check on the server. Reachability requires an authenticated adjacent-network session, and successful exploitation removes other users' comments from shared requirements records.
Summary
What happened
Broken access control in IBM DOORS Next 7.0.2, 7.0.3, and 7.1 allows remote authenticated users to delete comments owned by others. The comment-deletion workflow relies on client-side enforcement instead of applying the ownership authorization check on the server. Reachability requires an authenticated adjacent-network session, and successful exploitation removes other users' comments from shared requirements records.
The record
- CVE
- CVE-2025-2138
- Published
- Oct 12, 2025
- Updated
- Oct 14, 2025
- Vendor
- IBM
- Product
- IBM Engineering Requirements Management DOORS Next
- Classifications
- CWE-602, T1485
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 12, 2025CVE publishedPublication date reported by the CVE source.
- Oct 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=7.0.2
- Affected versionversion=7.0.3
- Affected versionversion=7.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo