CVE-2017-7221 json
OpenText Documentum Content Server has an inadequate protection mechanism against SQL injection, which allows remote authenticated users to…
published 2017-04-25 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-16256
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.3%
- EPSS 4.3% chance of exploitation in 30 days, percentile 91%
- public exploits
- 1
- Exploit-DB
Summary
OpenText Documentum Content Server has an inadequate protection mechanism against SQL injection, which allows remote authenticated users to execute arbitrary code with super-user privileges by leveraging the availability of the dm_bp_transition docbase method with a user-created dm_procedure object, as demonstrated by use of a backspace character in an injected string. NOTE: this vulnerability exists because of an incomplete fix for CVE-2014-2513.
Timeline
- First public exploit (EDB-41928)
- Published
Exploit prediction
4.31% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-41928 OpenText Documentum Content Server - dm_bp_transition.ebs docbase Method Arbitrary Code Execution webapps, 2017-04-25
- seclists.org http://seclists.org/fulldisclosure/2017/Apr/97 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
exploit-db.com
/exploits/41928/
exploit
-
seclists.org
/fulldisclosure/2017/Apr/97
exploit, mailing-list, third-party-advisory, vdb-entry
-
securityfocus.com
/bid/98038
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-7221
- NVD CVE-2017-7221
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.