Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 7.5 CISA Known Exploited Vulnerability

CVE-2022-36537

ZK Framework AuUploader Unspecified Vulnerability

ZK Framework AuUploader

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.

CVSS
7.5
HIGH
EPSS
95.4%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
26 Aug 2022
NVD

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 27 February 2023. US federal agencies were required to remediate it by 20 March 2023. CISA records this vulnerability as known to be used in ransomware campaigns.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 95.4%, which is higher than 99.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Frequently asked questions

Is CVE-2022-36537 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2022-36537.

What does CVE-2022-36537 affect?

CVE-2022-36537 affects ZK Framework AuUploader. 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.

How severe is CVE-2022-36537?

CVE-2022-36537 is rated HIGH with a CVSS base score of 7.5. EPSS puts the probability of exploitation in the next 30 days at 95.4%, higher than 99.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 20 March 2023.

How should organisations respond to CVE-2022-36537?

Apply the vendor patch for ZK Framework AuUploader as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.