CVE-2024-36514
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 8000 are vulnerable to the authenticated SQL injection in file summary 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 confidenceZohocorp ManageEngine ADAudit Plus versions below 8000 contain an authenticated SQL injection vulnerability in the file summary feature. An attacker with valid credentials can inject malicious SQL queries through this feature to manipulate database operations.
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.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.
-
Identify installed ADAudit Plus versionLocate the ADAudit Plus version information through the product's web interface, About page, or version file in the installation directoryAffected if The installed version is below 8.0 (versions 7.x and earlier)
-
Confirm file summary feature is accessibleNavigate to or identify the file summary feature within ADAudit Plus using an authenticated sessionAffected if The file summary feature exists and is accessible to authenticated users
-
Check for unauthorized database access patternsReview ADAudit Plus logs, database logs, or audit trails for suspicious SQL queries originating from the file summary featureAffected if Malicious or unexpected SQL queries appear in logs related to file summary operations
-
Verify credential exposureReview access logs for the file summary endpoint to identify if any unauthorized SQL injection attempts were made using valid credentialsAffected if Multiple SQL injection payloads are present in requests to the file summary feature
A user is affected if ADAudit Plus version is below 8.0 and the file summary feature is accessible to authenticated users who could inject SQL queries.
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 to ADAudit Plus version 8000 or later which contains the vendor patch for this vulnerability.
ManageEngine ADAudit Plus version 8000 or later
- Upgrade ManageEngine ADAudit Plus to version 8000 or later.
- After upgrading, verify the SQL injection vulnerability is resolved by reviewing release notes or changelog.
- Test the file summary functionality to ensure normal operation post-upgrade.
- Review user access controls and ensure only authorized administrators have access to the file summary feature.
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-36514 — 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-36514 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