dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 May 2022.
Manageengine Servicedesk PlusApplication · Zohocorp

CVE-2019-8394

MEDIUM · 6.5 CVSS v3.1 Published 2019-02-17
Fix available
A fix is available. Upgrade to 10.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable Zero-click

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 (SDP) before 10.0 build 10012 allows remote attackers to upload arbitrary files via login page customization.

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

Zoho ManageEngine ServiceDesk Plus versions prior to build 10012 contain an arbitrary file upload vulnerability in the login page customization feature, allowing remote attackers to upload malicious files to the server.

MitigationUpgrade ServiceDesk Plus to build 10012 or later. Restrict network access to the SDP administration interfaces and implement strict input validation on file upload functionality as a defense-in-depth measure.

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:< 10.0.0= 10.0.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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. Determine ServiceDesk Plus build number
    Access the ServiceDesk Plus administration interface or check the installation directory for version information. Navigate to the 'About' or 'Version Details' section in the admin console to locate the build number.
    Affected if The build number is less than 10012 (for example, 10000, 10010) or if the build cannot be determined and the version displays as 10.0.0 or earlier.
  2. Verify login page customization feature access
    Navigate to the login page of ServiceDesk Plus and check if a customization or branding option is available. In the admin interface, look for 'Login Page Settings' or 'Customize Login Page' under the administration or branding sections.
    Affected if The login page customization feature is present and accessible, indicating the vulnerable component is enabled.
  3. Confirm network exposure of login page
    Determine if the ServiceDesk Plus login page is accessible from the network. Attempt to access the login page URL (typically /login.do or /servicedesk/login) from an external or non-admin system.
    Affected if The login page is externally accessible without authentication, which would allow remote attackers to reach the vulnerable file upload functionality.
  4. Check for unauthorized uploaded files
    Review the ServiceDesk Plus web directory for unexpected files, particularly in locations where uploaded files may be stored (such as temporary directories, attachments folder, or custom branding asset folders).
    Affected if Unexpected or suspicious files are found in the web application directories, particularly PHP, JSP, or executable files that were not intentionally deployed.

A user is affected if their ServiceDesk Plus build is below 10012 (or version 10.0.0) AND the login page customization feature is accessible, allowing unauthenticated remote attackers to potentially upload malicious files.

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.0.0 or later
Fixed in 10.0.0
Interim mitigation

Upgrade ServiceDesk Plus to build 10012 or later. Restrict network access to the SDP administration interfaces and implement strict input validation on file upload functionality as a defense-in-depth measure.

Recommended fix Moderate confidence

ServiceDesk Plus 10.0 build 10012 or later

  1. 1. Backup your current ServiceDesk Plus installation and database
  2. 2. Download ServiceDesk Plus version 10.0 build 10012 or later from the official ManageEngine download portal
  3. 3. Stop the ServiceDesk Plus service
  4. 4. Run the upgrade installer on the existing installation directory
  5. 5. Follow the on-screen upgrade wizard prompts
  6. 6. Start the ServiceDesk Plus service after upgrade completes
  7. 7. Verify the login page customization functionality works correctly
  8. 8. Test that arbitrary file uploads are no longer possible through the login customization feature
Caveat Review release notes for version 10.0 build 10012 for any configuration or feature changes that may require adjustment

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

Fix this in Manageengine Servicedesk Plus Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2019-8394 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