CVE-2023-37308
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 ADAudit Plus before 7100 allows XSS via the username field.
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 scripting (XSS) vulnerability in Zoho ManageEngine ADAudit Plus allows attackers to inject malicious scripts through the username field. This is a stored XSS issue where malicious input is persisted and executed when other users view the affected data.
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< 7.0= 7.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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 ADAudit Plus installation path and versionLocate the ADAudit Plus installation directory (commonly C:\ManageEngine\ADAudit Plus or /opt/ManageEngine/ADAuditPlus) and check the version.txt or about page accessible via the admin console. Compare the installed version against the affected range: versions < 7.0 and version 7.0.Affected if The installed version is 7.0 or any version below 7.0.
-
Verify the product web interface is accessibleAccess the ADAudit Plus web console (typically https://localhost:8080 or port 8443) and confirm the application is running and reachable via browser.Affected if The web interface is exposed and users can authenticate to access the username-related features.
-
Confirm user management or user audit features are enabledWithin the ADAudit Plus console, navigate to the User Settings, User Auditing, or User Dashboard sections where username data is displayed. These are the areas where the stored XSS in the username field would be triggered.Affected if User auditing or user management features are active and display username information in the web interface.
You are affected if ADAudit Plus version 7.0 or below is installed, the web interface is accessible to users, and user auditing/management features are enabled where username data is displayed.
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 · scoped7.0
Upgrade ManageEngine ADAudit Plus to version 7100 or later, which contains the patch for this XSS vulnerability in the username field.
Build 7100 or later
- Check current build version of ManageEngine ADAudit Plus (typically in About or Settings)
- Download ManageEngine ADAudit Plus version 7100 or later from the official ManageEngine website (www.manageengine.com)
- Review ManageEngine official upgrade documentation before proceeding
- Backup current installation and database
- Install the upgraded version following standard upgrade procedures
- Verify the upgrade was successful and the XSS vulnerability in the username field is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37308 — 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-37308 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