# CVE-2025-1821: zj1983 zz ZorgAction.java getUserOrgForUserId sql injection

> Remote attackers can exploit SQL injection in the getUserOrgForUserId function to read or modify database contents.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **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:** 2 Mar 2025
- **Updated:** 3 Mar 2025
- **Also known as:** GHSA-qj3j-gr5j-56r7

## What is CVE-2025-1821?

CVE-2025-1821 is a medium-severity SQL injection vulnerability in zj1983 zz, published on 2 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in zj1983 zz up to 2024-8 and classified as critical. Affected by this issue is the function getUserOrgForUserId of the file src/main/java/com/futvan/z/system/zorg/ZorgAction.java. The manipulation of the argument userID leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2025-1821?

It affects 1 product.


Products: Zframeworks Zz.

## How do I fix CVE-2025-1821?

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

## Is CVE-2025-1821 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1821 exists.

## Other vulnerabilities in zj1983 zz

- [CVE-2025-1846](https://insights.sbomify.com/CVE-2025-1846/): zj1983 zz File ZfileAction.java deleteLocalFile denial of service (medium 5.3)
- [CVE-2025-1847](https://insights.sbomify.com/CVE-2025-1847/): zj1983 zz improper authorization (medium 5.3)
- [CVE-2025-1848](https://insights.sbomify.com/CVE-2025-1848/): zj1983 zz import_data_check server-side request forgery (medium 5.3)
- [CVE-2025-1849](https://insights.sbomify.com/CVE-2025-1849/): zj1983 zz import_data_todb server-side request forgery (medium 5.3)
- [CVE-2025-1812](https://insights.sbomify.com/CVE-2025-1812/): zj1983 zz SuperZ.java GetUserOrg sql injection (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1821 and fix it if it is affected.

What it is: CVE-2025-1821 is a medium-severity SQL injection vulnerability in zj1983 zz, published on 2 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1821 exists.

Affected product: zj1983 zz. 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-2025-1821/ (Markdown: https://insights.sbomify.com/CVE-2025-1821/index.md)
```

## Sources

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

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