CVE-2023-23075
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 · uneditedCross Site Scripting (XSS) vulnerability in Zoho Asset Explorer 6.9 via the credential name when creating a new Assets Workstation.
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 confidenceCross-site scripting (XSS) vulnerability in Zoho Asset Explorer 6.9 allows injection of malicious JavaScript through the credential name field when creating a new Assets Workstation. The application fails to properly sanitize user-supplied input before rendering it in the web page.
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.9CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 if Asset Explorer is installedCheck for ManageEngine Asset Explorer installation by looking for the product in installed programs (Windows) or checking common installation directories such as C:\Program Files\ManageEngine\AssetExplorer or /opt/ManageEngine/AssetExplorerAffected if Asset Explorer is not installed, the system is not affected by this specific CVE
-
Confirm the exact version numberAccess the Asset Explorer web interface and navigate to the About or Settings page, or check version.txt in the installation directory, to verify the installed version is exactly 6.9Affected if The installed version is exactly 6.9 - other versions may have different vulnerability status
-
Verify access to Assets Workstation creationLog into the Asset Explorer application and navigate to the Assets section, then attempt to access the Create Workstation or Add Workstation functionality where credential fields are availableAffected if The user has access to create or edit workstations with credential name fields in the web interface
-
Test for XSS in credential name fieldCreate a new Assets Workstation and insert a test XSS payload such as <script>alert(1)</script> into the credential name field, then save and view the resulting page to see if the script executesAffected if The JavaScript payload executes or is reflected unescaped in the page source, indicating the vulnerability is present
A user is affected if they have Zoho ManageEngine Asset Explorer version 6.9 installed and users can access the workstation creation feature with an unvalidated credential name field.
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 proper input validation and output encoding for the credential name field. Apply vendor patch from Zoho when available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23075 — 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-23075 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