# CVE-2022-36537: ZK Framework AuUploader Unspecified > Attackers can access sensitive information by sending a crafted POST request to the AuUploader component in ZK Framework. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Yes, since 27 Feb 2023 (CISA KEV), used in ransomware - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 26 Aug 2022 - **Updated:** 21 Oct 2025 - **Also known as:** GHSA-6278-2q4m-cmf3 ## What is CVE-2022-36537? CVE-2022-36537 is a high-severity vulnerability in n/a, published on 26 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description ZK Framework v9.6.1, 9.6.0.1, 9.5.1.3, 9.0.1.2 and 8.6.4.1 allows attackers to access sensitive information via a crafted POST request sent to the component AuUploader. ## Which versions are affected by CVE-2022-36537? 10 open source packages ship an affected version, including org.zkoss.zk:zk. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.zkoss.zk:zk` | Maven | All versions | 8.6.4.2 | | `org.zkoss.zk:zk` | Maven | All versions | 8.6.4.2 | | `org.zkoss.zk:zk` | Maven | From 9.0.0.0 | 9.0.1.3 | | `org.zkoss.zk:zk` | Maven | From 9.0.0.0 | 9.0.1.3 | | `org.zkoss.zk:zk` | Maven | From 9.5.0.0 | 9.5.1.4 | | `org.zkoss.zk:zk` | Maven | From 9.5.0.0 | 9.5.1.4 | | `org.zkoss.zk:zk` | Maven | From 9.6.0.0 | 9.6.0.2 | | `org.zkoss.zk:zk` | Maven | From 9.6.0.0 | 9.6.0.2 | | `org.zkoss.zk:zk` | Maven | From 9.6.1 | 9.6.2 | | `org.zkoss.zk:zk` | Maven | From 9.6.1 | 9.6.2 | Products: Zkoss Zk Framework. ## How do I fix CVE-2022-36537? Upgrade org.zkoss.zk:zk to a fixed version for your release line: 8.6.4.2, 9.0.1.3, 9.5.1.4 or 9.6.0.2. US federal agencies must fix it by 20 Mar 2023. ## Is CVE-2022-36537 being exploited? Yes. Attackers have exploited CVE-2022-36537 in the wild since at least 27 Feb 2023, including in ransomware campaigns. Public exploit code: - POC of CVE-2022-36537 (github_poc): https://github.com/Malwareman007/CVE-2022-36537 - CVE-2022-36537 (github_poc): https://github.com/agnihackers/CVE-2022-36537-EXPLOIT - https://github.com/ethan-repo-lab4b6/CVE-2022-36537 (github_poc): https://github.com/ethan-repo-lab4b6/CVE-2022-36537 - ZK Framework - Information Disclosure (nuclei): http/cves/2022/CVE-2022-36537.yaml ## Other vulnerabilities in n/a - [CVE-2013-5966](https://insights.sbomify.com/CVE-2013-5966/): Cross-site scripting in n/a (medium 4.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-36537 and fix it if it is affected. What it is: CVE-2022-36537 is a high-severity vulnerability in n/a, published on 26 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: Yes. Attackers have exploited CVE-2022-36537 in the wild since at least 27 Feb 2023, including in ransomware campaigns. Affected packages and fixed versions: - org.zkoss.zk:zk (Maven): affected all versions; fixed in 8.6.4.2 - org.zkoss.zk:zk (Maven): affected all versions; fixed in 8.6.4.2 - org.zkoss.zk:zk (Maven): affected from 9.0.0.0; fixed in 9.0.1.3 - org.zkoss.zk:zk (Maven): affected from 9.0.0.0; fixed in 9.0.1.3 - org.zkoss.zk:zk (Maven): affected from 9.5.0.0; fixed in 9.5.1.4 - org.zkoss.zk:zk (Maven): affected from 9.5.0.0; fixed in 9.5.1.4 - org.zkoss.zk:zk (Maven): affected from 9.6.0.0; fixed in 9.6.0.2 - org.zkoss.zk:zk (Maven): affected from 9.6.0.0; fixed in 9.6.0.2 - org.zkoss.zk:zk (Maven): affected from 9.6.1; fixed in 9.6.2 - org.zkoss.zk:zk (Maven): affected from 9.6.1; fixed in 9.6.2 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-36537/ (Markdown: https://insights.sbomify.com/CVE-2022-36537/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-36537 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-36537 - OSV: https://osv.dev/vulnerability/CVE-2022-36537 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-36537/ Summaries are generated and may contain mistakes; the official description above is the record.