CVE-2024-36485
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 · uneditedZohocorp ManageEngine ADAudit Plus versions below 8121 are vulnerable to SQL Injection in Technician reports option.
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 confidenceSQL injection vulnerability in the Technician reports feature of ManageEngine ADAudit Plus affecting versions prior to 8121. The vulnerability allows injection of malicious SQL queries through user-supplied input in the reports functionality.
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< 8.1= 8.1CVSS 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 ADAudit Plus installation and versionLocate the ManageEngine ADAudit Plus installation directory and check the version information, typically found in the product's about or version details within the application or in installation metadata.Affected if The installed version is 8.1 or any version prior to 8.1 (e.g., 7.x, 6.x, etc.).
-
Confirm Technician reports feature is accessibleVerify whether the Technician reports functionality is enabled and accessible within ADAudit Plus, typically found under the reports or technician section of the web interface.Affected if Technician reports feature is enabled and available to the user.
-
Review database query logs for anomaliesExamine database query logs or audit logs for unexpected or suspicious SQL statements, particularly those containing UNION, SELECT, DROP, or other SQL commands that could indicate injection attempts.Affected if Unusual or malicious SQL queries are present in the logs originating from Technician reports functionality.
You are affected if ADAudit Plus version is 8.1 or earlier and the Technician reports feature is accessible and being used, as this combination allows the SQL injection flaw to be exploited.
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 · scoped8.1
Upgrade ManageEngine ADAudit Plus to version 8121 or later to remediate this vulnerability.
Build 8121 or later (version 8.1 build 8121 and above)
- Verify current ADAudit Plus version by navigating to the About section in the admin console
- Backup the existing ADAudit Plus database and configuration files
- Download the latest ADAudit Plus installation package from the official ManageEngine download portal (www.manageengine.com/products/adaudit-plus)
- Stop the ADAudit Plus service before applying the upgrade
- Run the installer and follow the on-screen prompts to upgrade to build 8121 or later
- After upgrade completes, restart the ADAudit Plus service
- Verify the upgrade was successful by checking the build number in the About section
- Test the Technician reports functionality to confirm the SQL injection vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2024-36485 — 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-2024-36485 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