Threats / Zoho / CVE-2022-28810
CVE-2022-28810
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Zoho ManageEngine vulnerability
Zoho ManageEngine ADSelfService Plus contains an unspecified remote code execution vulnerability in password change and reset functionality, exploitable without authentication.
Verdict
Today item — known-exploited.
An unauthenticated attacker can execute arbitrary code by manipulating password reset or change operations in ADSelfService Plus. The vulnerability combines command injection (CWE-78) with hardcoded credentials or secrets (CWE-259), enabling direct system compromise.
CISA KEV Yes · 2023-03-074EPSS 0.70966 (verify live)5CVSS 6.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3Exploit Weaponized · public exploit · Metasploit module12
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-03-07).
Probability (EPSS)
EPSS 0.70966 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 6.8 (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H) · Affected: Zoho, ManageEngine. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-78 OS Command Injection, CWE-259 Hard-coded Password — weakness family: Injection, Authentication.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 323 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify that the password reset endpoint accepts unsanitized input that reaches system command execution.
Business
Attackers gain unauthenticated remote code execution on identity management infrastructure.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft a malicious password reset request containing shell metacharacters or command sequences.
Business
The vulnerability allows lateral movement into Active Directory and connected enterprise systems.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute commands with the privileges of the ManageEngine service account.
Business
Compromise of credential management systems leads to wholesale exposure of user accounts and administrative access.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05