# CVE-2024-1012: Wanhu ezOFFICE wf_printnum.jsp sql injection

> Remote attackers can exploit SQL injection in wf_printnum.jsp to read or modify database contents in Wanhu ezOFFICE.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 31 Jan 2024
- **Updated:** 13 Jun 2025
- **Also known as:** GHSA-39rp-fmqv-8wr2

## What is CVE-2024-1012?

CVE-2024-1012 is a medium-severity SQL injection vulnerability in Wanhu ezOFFICE, published on 31 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, has been found in Wanhu ezOFFICE 11.1.0. This issue affects some unknown processing of the file defaultroot/platform/bpm/work_flow/operate/wf_printnum.jsp. The manipulation of the argument recordId leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-252281 was assigned to this vulnerability.

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

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

It affects 1 product.


Products: Whir Ezoffice.

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

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

## Is CVE-2024-1012 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1012 is a medium-severity SQL injection vulnerability in Wanhu ezOFFICE, published on 31 Jan 2024. 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-2024-1012 exists.

Affected product: Wanhu ezOFFICE. 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-1012/ (Markdown: https://insights.sbomify.com/CVE-2024-1012/index.md)
```

## Sources

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

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