CVE-2024-36035
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 8003 are vulnerable to authenticated SQL Injection in user session recording.
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 confidenceThis is an authenticated SQL injection vulnerability in the user session recording feature of ManageEngine ADAudit Plus. An attacker with valid credentials can inject malicious SQL queries through this feature to potentially extract, modify, or delete sensitive data from the database.
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.0= 8.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
- 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.
-
Verify ManageEngine ADAudit Plus installationLocate the ADAudit Plus installation directory (commonly C:\Program Files\ManageEngine\ADAudit Plus or /opt/ManageEngine/ADAuditPlus) and confirm the product is presentAffected if ADAudit Plus is not installed on the system
-
Determine installed ADAudit Plus versionCheck the product version by opening the ADAudit Plus web interface and navigating to About page, or locate a version file in the installation directory such as version.txt or build.txtAffected if The installed version is 8.0 or any version below 8.0 (e.g., 7.x, 6.x, etc.)
-
Confirm user session recording feature is enabledIn the ADAudit Plus web interface, navigate to Administration > Features > User Session Recording, or check the configuration file for the session recording moduleAffected if User session recording feature is enabled and the version is in the affected range
The environment is affected if ManageEngine ADAudit Plus version 8.0 or below is installed with the user session recording feature enabled.
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.0
Upgrade ManageEngine ADAudit Plus to version 8003 or later to remediate this vulnerability.
Build 8003 or later
- 1. Identify the current installed version of ManageEngine ADAudit Plus
- 2. Create a complete backup of the ADAudit Plus installation directory and its database
- 3. Download the fixed version (build 8003 or later) from the official ManageEngine download portal
- 4. Stop the ADAudit Plus service before applying the upgrade
- 5. Follow ManageEngine's official upgrade documentation to install the update
- 6. Start the ADAudit Plus service and verify the application is running
- 7. Log in and verify that the SQL injection vulnerability is no longer present by testing the user session recording functionality
- 8. Review audit logs to ensure normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36035 — 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-36035 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