CVE-2024-5487
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 8110 are vulnerable to authenticated SQL Injection in attack surface analyzer's export 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 · high confidenceManageEngine ADAudit Plus versions below 8110 contain an authenticated SQL injection vulnerability in the attack surface analyzer's export functionality. An attacker with valid credentials can inject malicious SQL queries through the export parameter, potentially allowing data exfiltration or database compromise.
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 installed versionAccess the admin console and navigate to the About section, or check the version file in the installation directory to determine the running version numberAffected if The installed version is 8.1 or below (versions < 8.1 or = 8.1 are affected)
-
Verify attack surface analyzer module statusCheck if the Attack Surface Analyzer feature is enabled in the ADAudit Plus admin console under the relevant module configurationAffected if The attack surface analyzer module is active and accessible in the installation
-
Confirm export functionality accessibilityLocate the export option within the Attack Surface Analyzer section of the web interface and verify it is accessible with valid admin credentialsAffected if The export functionality in attack surface analyzer is reachable without additional restrictions beyond authentication
-
Review SQL injection indicators in logsExamine ADAudit Plus audit logs and database logs for unexpected SQL syntax, UNION queries, or anomalous database statements originating from attack surface analyzer export requestsAffected if Unusual SQL patterns appear in logs related to export operations
Your environment is affected if ADAudit Plus version is 8.1 or below and the attack surface analyzer export feature is accessible with valid credentials.
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 8110 or later to obtain the vendor patch for this SQL injection vulnerability.
Upgrade to ADAudit Plus version 8110 (8.1.1.0) or later
- Download ManageEngine ADAudit Plus version 8110 (8.1.1.0) or later from the official ManageEngine website
- Backup the current ADAudit Plus installation and database
- Install the upgraded version following the standard upgrade procedure
- Verify the SQL injection vulnerability is resolved by testing the attack surface analyzer's export option
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5487 — 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-5487 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