# CVE-2022-24848: SQL Injection in DHIS2's in OrgUnit program association

> Authenticated attackers can exploit SQL injection in the OrgUnit program association API to read, edit, and delete database data.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-52vp-f7hj-cj92

## What is CVE-2022-24848?

CVE-2022-24848 is a high-severity SQL injection vulnerability in dhis2-core, published on 1 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

DHIS2 is an information system for data capture, management, validation, analytics and visualization. A SQL injection security vulnerability affects the `/api/programs/orgUnits?programs=` API endpoint in DHIS2 versions prior to 2.36.10.1 and 2.37.6.1. The system is vulnerable to attack only from users that are logged in to DHIS2, and there is no known way of exploiting the vulnerability without first being logged in as a DHIS2 user. The vulnerability is not exposed to a non-malicious user and requires a conscious attack to be exploited. A successful exploit of this vulnerability could allow the malicious user to read, edit and delete data in the DHIS2 instance's database. Security patches are now available for DHIS2 versions 2.36.10.1 and 2.37.6.1. One may apply mitigations at the web proxy level as a workaround. More information about these mitigations is available in the GitHub Security Advisory.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2022-24848?

It affects 1 product.


Products: Dhis2 Dhis 2.

## How do I fix CVE-2022-24848?

No fix has been published for CVE-2022-24848 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-24848 being exploited?

There is no known exploitation of CVE-2022-24848 in the wild and no public exploit code.

## Other vulnerabilities in dhis2-core

- [CVE-2021-39179](https://insights.sbomify.com/CVE-2021-39179/): SQL Injection in DHIS2 Tracker API (high 8.8)
- [CVE-2021-32704](https://insights.sbomify.com/CVE-2021-32704/): Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in dhis2-core (high 8.5)
- [CVE-2021-41187](https://insights.sbomify.com/CVE-2021-41187/): SQL Injection in DHIS2 Tracker API (high 8.1)
- [CVE-2023-31138](https://insights.sbomify.com/CVE-2023-31138/): DHIS2 Core vulnerable to Improper Access Control with PATCH requests (high 7.1)
- [CVE-2022-41948](https://insights.sbomify.com/CVE-2022-41948/): Privilege Chaining with the user admin role in dhis2-core (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24848 and fix it if it is affected.

What it is: CVE-2022-24848 is a high-severity SQL injection vulnerability in dhis2-core, published on 1 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-24848 in the wild and no public exploit code.

Affected product: dhis2-core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-24848/ (Markdown: https://insights.sbomify.com/CVE-2022-24848/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24848
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24848
- OSV: https://osv.dev/vulnerability/CVE-2022-24848

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-24848/
Summaries are generated and may contain mistakes; the official description above is the record.