CVE-2022-28810
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 ADSelfService Plus before build 6122 allows a remote authenticated administrator to execute arbitrary operating OS commands as SYSTEM via the policy custom script feature. Due to the use of a default administrator password, attackers may be able to abuse this functionality with minimal effort. Additionally, a remote and partially authenticated attacker may be able to inject arbitrary commands into the custom script due to an unsanitized password field.
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 confidenceADSelfService Plus before build 6122 contains a command injection vulnerability in the policy custom script feature. An authenticated administrator can execute arbitrary OS commands as SYSTEM by injecting malicious commands into unsanitized fields. The presence of default administrator credentials further enables less-privileged or unauthenticated attackers to exploit this vulnerability.
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< 6.1= 6.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/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.
-
Identify the installed ADSelfService Plus build versionAccess the ADSelfService Plus admin console and navigate to the About or Help section to view the current build number, or check the build information displayed on the login pageAffected if The build number is less than 6122 (including version 6.1 and all builds below 6122)
-
Determine if the custom script policy feature is enabledIn the admin console, navigate to Policy Configuration or Customization settings and check if any policies have custom scripts configured or enabledAffected if Custom script policies are configured or enabled on the instance
-
Review all configured custom scripts for potential injection pointsExamine each custom script defined in the policy settings, looking for the use of password fields or user input variables that could be manipulatedAffected if Custom scripts contain unsanitized password fields or user-supplied input variables
-
Inspect the password field handling in custom script configurationsIn the policy custom script settings, specifically examine any password-related fields or parameters that are used within the scripts without sanitizationAffected if Password fields in custom scripts are not sanitized before being used in script execution
A user is affected if ADSelfService Plus is running a build less than 6122 AND has custom script policies configured with unsanitized password fields or user input
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 · scoped6.1
Upgrade ADSelfService Plus to build 6122 or later. If immediate patching is not possible, restrict access to the administrative interface, change default credentials, and disable the custom script policy feature until the upgrade can be completed.
ADSelfService Plus build 6122 or later (6.1 with build 6122+)
- 1. Back up the ADSelfService Plus installation directory and database before upgrading
- 2. Download the latest version of ManageEngine ADSelfService Plus from the official vendor website (www.manageengine.com/products/ad-self-service-plus/)
- 3. Ensure the build number is 6122 or higher, as this build contains the security fix for CVE-2022-28810
- 4. Stop the ADSelfService Plus service before proceeding with the upgrade
- 5. Run the upgrade installer and follow the on-screen prompts
- 6. After upgrade completes, verify the build number by navigating to About section in the admin console
- 7. Review and sanitize any existing custom script policies to ensure they do not contain malicious commands
- 8. Change the default administrator password immediately if not already done
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28810 — 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-2022-28810 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