CVE REMEDIATION GUIDE
CISA KEV · Known exploitedCriticalFixed-version data available

CVE-2022-47966 remediation guide

manageengine access manager plus, manageengine ad360

Multiple Zoho ManageEngine on-premise products, such as ServiceDesk Plus through 14003, allow remote code execution due to use of Apache Santuario xmlsec (aka XML Security for Java) 1.4.1, because the xmlsec XSLT features, by design in that version, make the application responsible for certain security protections, and the ManageEngine applications did not provide those protections. This affects Access Manager Plus before 4308, Active Directory 360 before 4310, ADAudit Plus before 7081, ADManager Plus before 7162, ADSelfService Plus before 6211, Analytics Plus before 5150, Application Contr...

Open CVE record
Productmanageengine access manager plus, manageengine ad360
Affected versions< 4.3, 4.3, < 7.0, 7.0, < 7.1, 7.1, < 6.2, 6.2, < 5.1, 5.1, < 6.9, 6.9, < 6.4, 6.4, < 5.7, 5.7, < 12.1, 12.1, < 14.0, 14.0
Fixed versions4.3, 7.0, 7.1, 6.2, 5.1, 6.9, 6.4, 5.7, 12.1, 14.0, 13.0, 10.1.2220.18, 11.1.2238.6, 10.1.2137.6, 1.1.2243.1, 10.1.2228.11, 10.1.41
Priority basisImmediate · CVSS 9.8 · EPSS 99.8%
01

Identify the affected asset

Confirm whether manageengine access manager plus, manageengine ad360 is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: < 4.3, 4.3, < 7.0, 7.0, < 7.1, 7.1, < 6.2, 6.2, < 5.1, 5.1, < 6.9, 6.9, < 6.4, 6.4, < 5.7, 5.7, < 12.1, 12.1, < 14.0, 14.0. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply updates per vendor instructions.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.