Privilege Chaining with the user admin role in dhis2-core
DHIS 2 is an open source information system for data capture, management, validation, analytics and visualization. Affected versions are subject to a privilege escalation vulnerability. A DHIS2 user with authority to manage users can assign superuser privileges to themself by manually crafting an HTTP PUT request. Only users with the following DHIS2 user role authorities can exploit this vulnerability. Note that in many systems the only users with user admin privileges are also superusers. In these cases, the escalation vulnerability does not exist. The vulnerability is only exploitable by attackers who can authenticate as users with the user admin authority. As this is usually a small and relatively trusted set of users, exploit vectors will often be limited. DHIS2 administrators should upgrade to the following hotfix releases: 2.36.12.1, 2.37.8.1, 2.38.2.1, 2.39.0.1. The only known workaround to this issue is to avoid the assignment of the user management authority to any users until the patch has been applied.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2022-41948
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 01:16 UTC · Revision 1
Source evidence
Privilege Chaining with the user admin role in dhis2-core
core-osv · Original sourcePublished 8 Dec 2022, 22:14 UTC
DHIS 2 is an open source information system for data capture, management, validation, analytics and visualization. Affected versions are subject to a privilege escalation vulnerability. A DHIS2 user with authority to manage users can assign superuser privileges to themself by manually crafting an HTTP PUT request. Only users with the following DHIS2 user role authorities can exploit this vulnerability. Note that in many systems the only users with user admin privileges are also superusers. In these cases, the escalation vulnerability does not exist. The vulnerability is only exploitable by attackers who can authenticate as users with the user admin authority. As this is usually a small and relatively trusted set of users, exploit vectors will often be limited. DHIS2 administrators should upgrade to the following hotfix releases: 2.36.12.1, 2.37.8.1, 2.38.2.1, 2.39.0.1. The only known workaround to this issue is to avoid the assignment of the user management authority to any users until the patch has been applied.
osv:CVE-2022-41948
Complete source record
{
"id": "7f4973767af99e9f29b472365ef11aad578ecde11954757ec6becd7ef36b6be0",
"url": "https://osv.dev/vulnerability/CVE-2022-41948",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Privilege Chaining with the user admin role in dhis2-core",
"summary": "DHIS 2 is an open source information system for data capture, management, validation, analytics and visualization. Affected versions are subject to a privilege escalation vulnerability. A DHIS2 user with authority to manage users can assign superuser privileges to themself by manually crafting an HTTP PUT request. Only users with the following DHIS2 user role authorities can exploit this vulnerability. Note that in many systems the only users with user admin privileges are also superusers. In these cases, the escalation vulnerability does not exist. The vulnerability is only exploitable by attackers who can authenticate as users with the user admin authority. As this is usually a small and relatively trusted set of users, exploit vectors will often be limited. DHIS2 administrators should upgrade to the following hotfix releases: 2.36.12.1, 2.37.8.1, 2.38.2.1, 2.39.0.1. The only known workaround to this issue is to avoid the assignment of the user management authority to any users until the patch has been applied.",
"evidence": "osv:CVE-2022-41948",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2022-41948",
"aliases": [
"CVE-2022-41948",
"GHSA-59fm-8432-2426"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/dhis2/dhis2-core",
"type": "GIT",
"events": [
{
"introduced": "b9e5b0f42c60359833d636c27c3c81a08bb2a128"
},
{
"fixed": "7368011a1ffef0d18a100b6cbc908e76ed05cc81"
},
{
"introduced": "b8d4ef368ffa769034b36e143551be28a671c12c"
},
{
"fixed": "21cbd23d560fc7a1414959af7890771726d8ce8d"
},
{
"introduced": "769bded6742261c68549654e8beacdcff2674c2a"
},
{
"fixed": "e590bdcd5488d9cde4a97acfab8c42970084b008"
},
{
"introduced": "3009509e8358b3c01815b48358e62492d3ae78d8"
},
{
"last_affected": "3009509e8358b3c01815b48358e62492d3ae78d8"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:dhis2:dhis_2:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "2.34.0"
},
{
"fixed": "2.36.12.1"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:dhis2:dhis_2:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "2.37.0"
},
{
"fixed": "2.37.8.1"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:dhis2:dhis_2:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "2.38.0"
},
{
"fixed": "2.38.2.1"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:dhis2:dhis_2:2.39.0:*:*:*:*:*:*:*",
"range": [
{
"introduced": "2.39.0"
},
{
"last_affected": "2.39.0"
}
],
"source": "CPE_STRING"
}
]
}
}
],
"versions": [
"2.39.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-41948.json"
}
}
],
"modified": "2026-10-28T02:30:32.396311671Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/41xxx/CVE-2022-41948.json",
"https://github.com/dhis2/dhis2-core/security/advisories/GHSA-59fm-8432-2426",
"https://nvd.nist.gov/vuln/detail/CVE-2022-41948"
],
"provider_metadata": {
"cwe_ids": [
"CWE-269"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/41xxx/CVE-2022-41948.json"
}
},
"related_cves": [
{
"value": "CVE-2022-41948",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 499420,
"published_at": "2022-12-08T22:14:12.992+00:00"
}