CVE-2023-38743
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 · uneditedZoho ManageEngine ADManager Plus before Build 7200 allows admin users to execute commands on the host machine.
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 confidenceThis is a command injection vulnerability in Zoho ManageEngine ADManager Plus that allows authenticated admin users to execute arbitrary operating system commands on the host machine. The vulnerability exists in versions prior to Build 7200 and enables privilege escalation from application administrator to full system-level access.
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< 7.2CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify ADManager Plus installationCheck for the ADManager Plus installation directory (commonly at C:\ManageEngine\ADManager Plus on Windows or /opt/ADManager Plus on Linux) and verify the product is running as a service.Affected if The product is installed and running on the system.
-
Identify installed version and build numberLocate the version file or access the About page in the ADManager Plus admin console. The build number is typically displayed in the product UI footer or in a version.txt file within the installation directory.Affected if Unable to determine version information from the installation.
-
Compare version against affected rangeCompare your identified build number to Build 7200 (or version 7.2). Versions prior to Build 7200 are affected by this vulnerability.Affected if Your installed build number is less than 7200 (for example, 7180, 7150, etc.) or your version displays as 7.1 or earlier.
-
Confirm admin accounts existVerify that administrative user accounts are configured in ADManager Plus. This vulnerability requires authenticated admin access to exploit, so the presence of admin accounts indicates a potential attack vector.Affected if Admin users are configured and the admin console is network-accessible.
-
Review logs for suspicious command executionExamine ADManager Plus audit logs and server logs for unexpected commands or scripts executed from the application. Look for patterns indicating OS command execution that did not originate from legitimate administrative tasks.Affected if Logs show command execution activity that matches known exploitation patterns or is unexplained by authorized administrator actions.
If ADManager Plus is installed with a build number below 7200 (or version below 7.2) and admin access is configured, the environment is affected by CVE-2023-38743.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.2
Upgrade ManageEngine ADManager Plus to Build 7200 or later to apply the vendor patch. If immediate patching is not possible, restrict administrative access to trusted personnel and monitor for suspicious command execution activity.
ADManager Plus version 7.2 (Build 7200)
- 1. Log in to ADManager Plus as an administrator
- 2. Navigate to the About or Settings section to verify the current build number (ensure it is below Build 7200)
- 3. Download ADManager Plus version 7.2 (Build 7200) or later from the official ManageEngine download portal at www.manageengine.com
- 4. Review the upgrade instructions in the ADManager Plus Administration Guide
- 5. Create a full backup of the ADManager Plus installation, including the database and configuration files
- 6. Stop the ADManager Plus service before upgrading
- 7. Run the upgrade installer for Build 7200
- 8. Start the ADManager Plus service after upgrade completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38743 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-38743 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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