Skip to content

CVE-2022-47966

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 Control Plus before 10.1.2220.18, Asset Explorer before 6983, Browser Security Plus before 11.1.2238.6, Device Control Plus before 10.1.2220.18, Endpoint Central before 10.1.2228.11, Endpoint Central MSP before 10.1.2228.11, Endpoint DLP before 10.1.2137.6, Key Manager Plus before 6401, OS Deployer before 1.1.2243.1, PAM 360 before 5713, Password Manager Pro before 12124, Patch Manager Plus before 10.1.2220.18, Remote Access Plus before 10.1.2228.11, Remote Monitoring and Management (RMM) before 10.1.41. ServiceDesk Plus before 14004, ServiceDesk Plus MSP before 13001, SupportCenter Plus before 11026, and Vulnerability Manager Plus before 10.1.2220.18. Exploitation is only possible if SAML SSO has ever been configured for a product (for some products, exploitation requires that SAML SSO is currently active).

CVSS
9.8Criticalscored by CISA
Exploited in the wild
Yes, in CISA KEV since 23 Jan 2023CISA deadline for US federal agencies: 13 Feb 2023known use in ransomware campaignspublic exploit code
EPSS
99.8%chance of exploitation in the next 30 daystop 0.1% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
18 Jan 2023analysed here 12 Nov 2026

Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)

Summary

Triage

Exploitable
At runtime
Attack vector
network
Weakness
  • CWE-20 Improper Input Validation
Can a WAF block it?
Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

  • zohocorp:manageengine_access_manager_plus
  • zohocorp:manageengine_ad360
  • zohocorp:manageengine_adaudit_plus
  • zohocorp:manageengine_admanager_plus
  • zohocorp:manageengine_adselfservice_plus
  • zohocorp:manageengine_analytics_plus
  • zohocorp:manageengine_assetexplorer
  • zohocorp:manageengine_key_manager_plus
  • zohocorp:manageengine_pam360
  • zohocorp:manageengine_password_manager_pro
  • zohocorp:manageengine_servicedesk_plus
  • zohocorp:manageengine_servicedesk_plus_msp
  • zohocorp:manageengine_supportcenter_plus
  • zohocorp:manageengine_application_control_plus
  • zohocorp:manageengine_browser_security_plus
  • zohocorp:manageengine_device_control_plus
  • zohocorp:manageengine_endpoint_dlp_plus
  • zohocorp:manageengine_os_deployer
  • zohocorp:manageengine_patch_manager_plus
  • zohocorp:manageengine_remote_access_plus
  • zohocorp:manageengine_remote_monitoring_and_management_central
  • zohocorp:manageengine_vulnerability_manager_plus

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.

Also consider: patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 23 Jan 2023. Known use in ransomware campaigns.
CISA due date
13 Feb 2023, the remediation deadline for US federal agencies
CISA required action
Apply updates per vendor instructions.
Public exploit code
Yes: 3 Metasploit modules · 5 GitHub proofs of concept · 1 Nuclei template
CISA SSVC
exploitation active, automatable yes, technical impact totalAssessed by CISA 13 Jan 2023 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 13 Jan 2023CISA SSVC assessment: exploitation active
  2. 17 Jan 2023First public exploit or proof of concept4 days later
  3. 18 Jan 2023Published2 days later
  4. 23 Jan 2023Added to CISA KEV (exploited in the wild)4 days later
  5. 13 Feb 2023CISA remediation due date (US federal agencies)21 days later
  6. 31 Jul 2026CVE record last updated1,264 days (about 3 years) later
  7. 12 Nov 2026Analysed by vulneraibility.com104 days (about 3 months) later

CVSS vector

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

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2022-47966 being exploited?

Yes. CVE-2022-47966 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2022-47966?

CVE-2022-47966 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2022-47966?

Yes. A fix has been recorded for CVE-2022-47966. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2022-47966 affect?

CVE-2022-47966 affects zohocorp:manageengine_access_manager_plus, zohocorp:manageengine_ad360, zohocorp:manageengine_adaudit_plus, zohocorp:manageengine_admanager_plus, and 18 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

11 references in the CVE record, grouped by the tags the record gives them.

Other links (11)

Show 5 more
  • github.com /horizon3ai/CVE-2022-47966
  • horizon3.ai /manageengine-cve-2022-47966-technical-deep-dive/
  • cisa.gov /news-events/cybersecurity-advisories/aa23-250a
  • attackerkb.com /topics/gvs0Gv8BID/cve-2022-47966/rapid7-analysis
  • cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-47966

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com