Manageengine Adaudit PlusApplication · Zohocorp

CVE-2023-49331

HIGH · 8.8 CVSS v3.1 Published 2024-05-20
Fix available
A fix is available. Upgrade to 7.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Zoho ManageEngine ADAudit Plus versions below 7271 allows SQL injection in the aggregate reports search 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 confidence

SQL injection vulnerability in the aggregate reports search option of Zoho ManageEngine ADAudit Plus versions prior to 7271. Attackers can inject malicious SQL queries through unsanitized search input to access, modify, or delete database contents.

MitigationUpgrade ManageEngine ADAudit Plus to version 7271 or later to apply the vendor patch that addresses the SQL injection vulnerability.

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
Manageengine Adaudit PlusApplication
Affected:< 7.2= 7.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if ManageEngine ADAudit Plus is installed
    Check for the ADAudit Plus service running on the system, or locate the installation directory (typically C:\ManageEngine\ADAuditPlus or /opt/ManageEngine/ADAuditPlus)
    Affected if ADAudit Plus software is found on the system
  2. Determine the installed ADAudit Plus version
    Access the ADAudit Plus web interface and navigate to Home > About, or check the version.txt file in the installation directory
    Affected if The installed version is 7.2 or any version prior to 7.2 (e.g., 7.1, 7.0, 6.x)
  3. Verify the aggregate reports feature is accessible
    Log into the ADAudit Plus web interface and check if the Reports > Aggregate Reports section is available in the navigation menu
    Affected if The aggregate reports feature is present and accessible to the user account
  4. Confirm web interface is network-accessible
    Attempt to access the ADAudit Plus login page via browser using the server hostname or IP address on the configured port (default 8081 or 8443)
    Affected if The ADAudit Plus web interface is reachable from network locations (indicating external attack surface)

If ADAudit Plus is installed and the version is 7.2 or any version prior to 7.2 with the aggregate reports feature accessible, the environment is affected by this SQL injection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.2 or later
Fixed in 7.2
Interim mitigation

Upgrade ManageEngine ADAudit Plus to version 7271 or later to apply the vendor patch that addresses the SQL injection vulnerability.

Recommended fix Moderate confidence

ADAudit Plus build 7271 or later within the 7.2 series (or next stable release)

  1. 1. Identify current build version of ManageEngine ADAudit Plus by checking the About or version information in the product UI
  2. 2. Download the latest ManageEngine ADAudit Plus version (build 7271 or higher) from the official ManageEngine download portal at www.manageengine.com/products/adaudit-plus
  3. 3. Before upgrading, take a full backup of the ADAudit Plus database and configuration files
  4. 4. Stop the ADAudit Plus service to ensure a clean upgrade process
  5. 5. Install the updated version (build 7271 or newer) which contains the SQL injection fix for the aggregate reports search option
  6. 6. After installation, verify the service starts successfully and confirm the new build version in the product UI
  7. 7. Test the aggregate reports search functionality to ensure the vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Manageengine Adaudit Plus Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49331 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-49331 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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