# CVE-2024-11961: Guangzhou Huayi Intelligent Technology Jeewms WmOmNoticeHController.java preHandle information disclosure

> Remote attackers can exploit a flaw in the preHandle function to disclose sensitive information from the Jeewms warehouse management system.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Nov 2024
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-89c4-58v4-9j7x

## What is CVE-2024-11961?

CVE-2024-11961 is a medium-severity vulnerability in Guangzhou Huayi Intelligent Technology Jeewms, published on 28 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in Guangzhou Huayi Intelligent Technology Jeewms 3.7. It has been rated as problematic. This issue affects the function preHandle of the file src/main/java/com/zzjee/wm/controller/WmOmNoticeHController.java. The manipulation of the argument request leads to information disclosure. The attack may be initiated 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-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-11961?

It affects 1 product.


Products: Huayi-Tec Jeewms.

## How do I fix CVE-2024-11961?

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

## Is CVE-2024-11961 being exploited?

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

## Other vulnerabilities in Guangzhou Huayi Intelligent Technology Jeewms

- [CVE-2025-60269](https://insights.sbomify.com/CVE-2025-60269/): SQL injection in n/a (critical 9.4)
- [CVE-2024-57761](https://insights.sbomify.com/CVE-2024-57761/): File upload in n/a (high 8.1)
- [CVE-2025-0390](https://insights.sbomify.com/CVE-2025-0390/): Guangzhou Huayi Intelligent Technology Jeewms wmOmNoticeHController.do path traversal (medium 6.9)
- [CVE-2024-12347](https://insights.sbomify.com/CVE-2024-12347/): Guangzhou Huayi Intelligent Technology Jeewms Druid Monitoring Interface index.html improper authorization (medium 6.9)
- [CVE-2025-70311](https://insights.sbomify.com/CVE-2025-70311/): SQL injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11961 and fix it if it is affected.

What it is: CVE-2024-11961 is a medium-severity vulnerability in Guangzhou Huayi Intelligent Technology Jeewms, published on 28 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-11961 in the wild and no public exploit code.

Affected product: Guangzhou Huayi Intelligent Technology Jeewms. 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-2024-11961/ (Markdown: https://insights.sbomify.com/CVE-2024-11961/index.md)
```

## Sources

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

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