CVE-2019-11361
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 Remote Access Plus 10.0.258 does not validate user permissions properly, allowing for privilege escalation and eventually a full application takeover.
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 · moderate confidenceZoho ManageEngine Remote Access Plus 10.0.258 contains an improper authorization vulnerability where the application fails to validate user permissions correctly. This allows authenticated users to bypass permission checks, escalate their privileges, and ultimately achieve full application 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= 10.0.258CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify the installed version of ManageEngine Remote Access PlusAccess the product's web interface and navigate to the About or Help section, or check the installation directory for a version file. The product typically displays the version on the login page footer or in Admin > Settings > Product Information.Affected if The installed version is 10.0.258 exactly.
-
Confirm the application web interface is accessibleVerify that the Remote Access Plus web console is reachable by accessing the application's URL (typically on port 8060 or 8061). Attempt to log in with any valid user account.Affected if The application is accessible and responds, indicating the service is running.
-
Check for existing user accounts and rolesLog into the admin console and navigate to Admin > Users or Admin > User Management to view configured users and their assigned roles/permission levels.Affected if Multiple user roles exist (such as standard user, technician, and administrator) and the application relies on role-based access control.
-
Verify permission enforcement on sensitive operationsUsing a low-privilege authenticated user account, attempt to access administrative functions or resources outside the assigned permission scope, such as modifying system settings or accessing other user data.Affected if A lower-privilege user can perform actions beyond their assigned role permissions, indicating the authorization bypass is present.
A user is affected if they are running version 10.0.258 of ManageEngine Remote Access Plus with the web interface accessible and multiple user roles configured.
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 dataUpgrade to a patched version of ManageEngine Remote Access Plus and ensure all permission checks are properly enforced throughout the application authorization framework.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11361 — 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-11361 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