Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Dec 2021.
Manageengine Servicedesk PlusApplication · Zohocorp

CVE-2021-44077

CRITICAL · 9.8 CVSS v3.1 Published 2021-11-29
Fix available
A fix is available. Upgrade to 10.5 / 11.0 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Zoho ManageEngine ServiceDesk Plus before 11306, ServiceDesk Plus MSP before 10530, and SupportCenter Plus before 11014 are vulnerable to unauthenticated remote code execution. This is related to /RestAPI URLs in a servlet, and ImportTechnicians in the Struts configuration.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Unauthenticated remote code execution vulnerability in Zoho ManageEngine ServiceDesk Plus, ServiceDesk Plus MSP, and SupportCenter Plus. The flaw resides in the /RestAPI servlet and is tied to the ImportTechnicians functionality in Struts configuration, allowing remote attackers to execute arbitrary code without any authentication.

MitigationImmediately upgrade to patched versions: ServiceDesk Plus 11306+, ServiceDesk Plus MSP 10530+, or SupportCenter Plus 11014+. Until patched, consider network segmentation or restricting access to /RestAPI endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Manageengine Servicedesk PlusApplication
Affected:< 11.1= 11.1= 11.2= 11.3
Manageengine Servicedesk Plus MspApplication
Affected:< 10.5= 10.5
Manageengine Supportcenter PlusApplication
Affected:< 11.0= 11.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed product and version
    Access the application admin console or check the application's 'About' or 'Version' page typically found in the Help or Administrator settings. For Zoho ManageEngine products, the version is often displayed on the login page or in the header area.
    Affected if The installed version is ServiceDesk Plus 11.1, 11.2, or 11.3; ServiceDesk Plus MSP 10.5 or below; or SupportCenter Plus 11.0 or below.
  2. Confirm the product type
    Determine whether the installation is ServiceDesk Plus, ServiceDesk Plus MSP, or SupportCenter Plus. This is visible in the product name on the login page or in the application header.
    Affected if The product is any of the three affected products: ServiceDesk Plus, ServiceDesk Plus MSP, or SupportCenter Plus.
  3. Check for /RestAPI endpoint exposure
    Attempt to access the /RestAPI endpoint by sending a request to https://<your-server>/RestAPI/ or check network logs and firewall rules to see if this endpoint is externally accessible.
    Affected if The /RestAPI endpoint is reachable from an untrusted network without authentication.
  4. Verify ImportTechnicians action availability
    Check if the ImportTechnicians Struts action is present by examining the application's web.xml or struts configuration files, or by attempting to access a URL pattern like /RestAPI/ImportTechnicians (note: do not actually exploit, only verify the endpoint exists).
    Affected if The ImportTechnicians action is accessible and responds to requests.
  5. Review authentication enforcement on affected endpoints
    Test the /RestAPI endpoint with an unauthenticated request to confirm whether the application requires valid credentials before allowing access to sensitive API functions.
    Affected if The /RestAPI endpoint or ImportTechnicians action can be accessed without providing any authentication credentials.

You are affected if you are running any of the vulnerable versions (ServiceDesk Plus 11.1-11.3, ServiceDesk Plus MSP 10.5 or lower, or SupportCenter Plus 11.0 or lower) AND the /RestAPI endpoint is accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.5 / 11.0 / 11.1 or later
Fixed in 10.511.011.1
Interim mitigation

Immediately upgrade to patched versions: ServiceDesk Plus 11306+, ServiceDesk Plus MSP 10530+, or SupportCenter Plus 11014+. Until patched, consider network segmentation or restricting access to /RestAPI endpoints.

Recommended fix High confidence

ServiceDesk Plus: 11.1 build 11306+ (latest 11.x); ServiceDesk Plus MSP: 10.5 build 10530+ (latest 10.x); SupportCenter Plus: 11.0 build 11014+ (latest 11.x)

  1. 1. Identify the currently installed ManageEngine product and version (ServiceDesk Plus, ServiceDesk Plus MSP, or SupportCenter Plus)
  2. 2. For ServiceDesk Plus: Upgrade to version 11.1 build 11306 or later (or the latest 11.x stable release)
  3. 3. For ServiceDesk Plus MSP: Upgrade to version 10.5 build 10530 or later (or the latest 10.x stable release)
  4. 4. For SupportCenter Plus: Upgrade to version 11.0 build 11014 or later (or the latest 11.x stable release)
  5. 5. Download the patch from the official ManageEngine support portal (pitstop.manageengine.com)
  6. 6. Back up the current installation and database before applying the upgrade
  7. 7. Apply the upgrade following ManageEngine's documented upgrade procedure
  8. 8. Verify the upgrade was successful and the /RestAPI endpoints now require authentication
Caveat Standard upgrade precautions apply - test in non-production environment first; review release notes for any feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Manageengine Servicedesk Plus Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-44077 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-44077 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data