CVE-2019-18411
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 5.x through 5803 has CSRF on the users' profile information page. Users who are attacked with this vulnerability will be forced to modify their enrolled information, such as email and mobile phone, unintentionally. Attackers could use the reset password function and control the system to send the authentication code back to the channel that the attackers own.
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 confidenceCross-Site Request Forgery vulnerability in Zoho ManageEngine ADSelfService Plus 5.x through 5803 allows attackers to trick authenticated users into modifying their profile information (email, mobile phone) via forged requests. Attackers can leverage this to hijack the password reset flow by changing the user's recovery email/phone to attacker-controlled channels, enabling unauthorized password resets and account takeover.
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= 5.0= 5.1= 5.2= 5.3= 5.4= 5.5= 5.6= 5.7= 5.8CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 installed ADSelfService Plus versionCheck the product version in the administration console or by reviewing the product's About/Version information pageAffected if The installed version is 5.0, 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, 5.7, or 5.8 (all versions through 5803)
-
Verify if user profile modification is enabledConfirm that the self-service profile update feature is active for end users in the product configurationAffected if The profile self-update feature is enabled and the version is within the affected range
-
Inspect profile update form for anti-CSRF protectionExamine the HTML source of the user profile modification page to determine if a unique anti-CSRF token is present in the form submissionAffected if No anti-CSRF token is found in the profile update form
-
Verify cookie security configurationsInspect Set-Cookie headers or cookie settings to check if SameSite attribute is configured on session cookiesAffected if SameSite cookie attribute is missing or set to None
-
Check referrer validation implementationReview the application's request handling to determine if HTTP Referrer header validation is performed before processing profile changesAffected if No referrer validation is implemented for profile update requests
If the installed version is 5.0-5.8 and the user profile update feature is accessible without proper anti-CSRF tokens, SameSite cookies, or referrer validation, the environment is vulnerable to CVE-2019-18411
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.
From vendor dataImplement anti-CSRF tokens on all state-changing operations, particularly the user profile page. Additionally, configure SameSite cookie attributes and implement proper referrer validation to prevent CSRF attacks.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18411 — 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-2019-18411 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