CVE-2024-21791
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 versions below 7271 allows SQL Injection in lockout history option. Note: Non-admin users cannot exploit this vulnerability.
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 confidenceSQL injection vulnerability in the lockout history feature of Zoho ManageEngine ADAudit Plus versions prior to 7271 allows authenticated administrators to inject malicious SQL queries through unsanitized input, potentially leading to unauthorized database access or data exfiltration.
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.2= 7.2CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Confirm ADAudit Plus installationLocate the ADAudit Plus installation directory, typically in C:\Program Files\ManageEngine\ADAudit Plus or /opt/ManageEngine/ADAudit Plus on Linux. Check for the presence of the ADAudit Plus service or executable files.Affected if ADAudit Plus is not installed on the system.
-
Determine installed versionOpen the ADAudit Plus console and navigate to Help > About, or check the build number in the installation logs or the version.txt file in the installation directory.Affected if The version displayed is prior to 7.2 or shows exactly version 7.2.
-
Compare version to vulnerable rangeIf the version is displayed as a full build number (e.g., 7270, 7260), verify it is less than 7271. If displayed as minor version (e.g., 7.1, 7.2), note that versions below 7.2 and exactly 7.2 are affected.Affected if The installed build number is less than 7271, or the minor version is 7.2 or lower.
-
Verify lockout history feature accessIn the ADAudit Plus web interface, navigate to the Lockouts section under the Domain Auditing tab to confirm the lockout history feature is accessible.Affected if The lockout history feature is present and accessible to authenticated administrators.
The system is affected if ADAudit Plus is installed with a version prior to build 7271 (or version 7.2 and below), exposing the lockout history feature to potential SQL injection.
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.2
Upgrade ManageEngine ADAudit Plus to version 7271 or later to remediate the SQL injection vulnerability.
ADAudit Plus version 7.3 (build 7271 or later)
- Upgrade ManageEngine ADAudit Plus to version 7271 or later (which corresponds to version 7.3)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21791 — 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-21791 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