CVE-2023-31138 json
DHIS2 Core vulnerable to Improper Access Control with PATCH requests
published 2023-05-09 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-35458
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 49%
- public exploits
- 0
- none known
Summary
DHIS2 Core contains the service layer and Web API for DHIS2, an information system for data capture. Starting in the 2.36 branch and prior to versions 2.37.9.1, 2.38.3.1, and 2.39.1.2, using object model traversal in the payload of a PATCH request, authenticated users with write access to an object may be able to modify related objects that they should not have access to. DHIS2 implementers should upgrade to a supported version of DHIS2 to receive a patch: 2.37.9.1, 2.38.3.1, or 2.39.1.2. It is possible to work around this issue by blocking all PATCH requests on a reverse proxy, but this may cause some issues with the functionality of built-in applications using legacy PATCH requests.
Patch / fix
- dhis2 dhis_2 2.37.9.1, 2.38.3.1, 2.39.1.2
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 21 mo ago
Exploit prediction
0.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected products
- dhis2 dhis2-core
Classification
References
-
github.com
/dhis2/dhis2-core/security/advisories/GHSA-pwvw-4m67-f4g2
third-party-advisory
-
github.com
/dhis2/dhis2-releases/blob/master/releases/2.37/ReleaseNote-2.37.9.1.md
release-notes
-
github.com
/dhis2/dhis2-releases/blob/master/releases/2.38/ReleaseNote-2.38.3.1.md
release-notes
-
github.com
/dhis2/dhis2-releases/blob/master/releases/2.39/ReleaseNote-2.39.1.2.md
release-notes
Sources
- CVE List CVE-2023-31138
- NVD CVE-2023-31138
Fencer Vulns 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.