CVE-2012-2315 json
admin/Auth in OpenKM 5.1.7 and other versions before 5.1.8-2 does not properly enforce privileges for changing user roles, which allows rem…
published 2012-09-09 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-2308
- cvss
- 4.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.2%
- EPSS 6.2% chance of exploitation in 30 days, percentile 93%
- public exploits
- 1
- Exploit-DB
Summary
admin/Auth in OpenKM 5.1.7 and other versions before 5.1.8-2 does not properly enforce privileges for changing user roles, which allows remote authenticated users to assign administrator privileges to arbitrary users via the userEdit action.
Timeline
- First public exploit (EDB-18888)
- Published
Exploit prediction
6.22% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-18888 OpenKM Document Management System 5.1.7 - Command Execution webapps, 2012-01-03
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
secunia.com
/advisories/47424
third-party-advisory, vendor-advisory
-
openwall.com
/lists/oss-security/2012/03/23/6
mailing-list
-
openwall.com
/lists/oss-security/2012/05/04/2
mailing-list
-
securityfocus.com
/bid/51250
vdb-entry
-
archives.neohapsis.com
/archives/bugtraq/2012-01/0007.html
mailing-list
-
openwall.com
/lists/oss-security/2012/03/23/8
mailing-list
-
archives.neohapsis.com
/archives/bugtraq/2012-01/0021.html
mailing-list
-
openwall.com
/lists/oss-security/2012/05/04/13
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/72112
vdb-entry
-
openwall.com
/lists/oss-security/2012/04/27/6
mailing-list
-
osvdb.org
/78105
vdb-entry
Sources
- CVE List CVE-2012-2315
- NVD CVE-2012-2315
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.