CVE-2023-26600
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 · uneditedManageEngine ServiceDesk Plus through 14104, ServiceDesk Plus MSP through 14000, Support Center Plus through 14000, and Asset Explorer through 6987 allow privilege escalation via query reports.
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 confidenceThis is a privilege escalation vulnerability in ManageEngine products (ServiceDesk Plus, ServiceDesk Plus MSP, Support Center Plus, and Asset Explorer) affecting versions prior to 14104/14000/14000/6987 respectively. The flaw exists in the query reports functionality and allows authenticated users with limited privileges to elevate their access rights beyond what their account should permit.
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.9= 6.9< 14.1= 14.1< 13.0= 13.0< 11.0= 11.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 ManageEngine productLocate the product by checking for install directories such as C:\ManageEngine\ServiceDesk Plus, C:\ManageEngine\SupportCenter Plus, or C:\ManageEngine\AssetExplorer, or look for running processes named ServiceDesk, SupportCenter, or AssetExplorer in Task ManagerAffected if One of the four affected products is installed
-
Check installed product versionOpen the About or version info page in the product admin console, or check the build number in the product's install directory (often in a version.txt, buildinfo, or similar file)Affected if Version is AssetExplorer <= 6.9, ServiceDesk Plus <= 14.1, ServiceDesk Plus MSP <= 13.0, or SupportCenter Plus <= 11.0
-
Verify query reports functionality existsLog into the product with a standard user account and navigate to the Reports or Query Reports section. Check if the feature is present in the menu or accessible via URL patterns like /reports/query.do or /sdpui/reportsAffected if Query reports feature is present and accessible to authenticated users
-
Check for limited-privilege user accountsReview user roles and permissions in the admin console under Users or Roles management. Look for non-admin users with Report or Query access permissionsAffected if Non-admin authenticated users exist with access to reporting features
-
Confirm privilege boundary configurationExamine the user role definitions to see if users with limited roles can create or modify query reports that could reference administrative data or functionsAffected if Limited-privilege users can access query report creation or modification functionality
A user is affected if they have an unpatched ManageEngine product (AssetExplorer <= 6.9, ServiceDesk Plus <= 14.1, ServiceDesk Plus MSP <= 13.0, or SupportCenter Plus <= 11.0) with query reports feature accessible to authenticated non-admin users.
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.911.013.0
Upgrade to ServiceDesk Plus version 14105 or higher, ServiceDesk Plus MSP version 14001 or higher, Support Center Plus version 14001 or higher, or Asset Explorer version 6988 or higher. Apply the appropriate patch from ManageEngine and verify the upgrade removes the privilege escalation vector in query reports.
AssetExplorer: 6.9.0 or later; ServiceDesk Plus: 14.1.0 or later; ServiceDesk Plus MSP: 13.0.0 or later; SupportCenter Plus: 11.0.0 or later
- 1. Identify the specific ManageEngine product in use (AssetExplorer, ServiceDesk Plus, ServiceDesk Plus MSP, or SupportCenter Plus).
- 2. Determine the current installed version by accessing the About or Admin section of the application.
- 3. For AssetExplorer users: Upgrade to version 6.9.0 or later (if not already at a fixed release).
- 4. For ServiceDesk Plus users: Upgrade to version 14.1.0 or later (if not already at a fixed release).
- 5. For ServiceDesk Plus MSP users: Upgrade to version 13.0.0 or later (if not already at a fixed release).
- 6. For SupportCenter Plus users: Upgrade to version 11.0.0 or later (if not already at a fixed release).
- 7. Download the latest version from the official ManageEngine downloads page: https://www.manageengine.com/
- 8. Before upgrading, perform a complete backup of the application data and database.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26600 — 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-26600 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