Manageengine Adaudit PlusApplication · Zohocorp

CVE-2023-49335

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 while getting file server details.

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 Zoho ManageEngine ADAudit Plus versions below 7271, specifically in the file server details functionality. Attackers can inject malicious SQL queries through unsanitized input, potentially allowing unauthorized database access, data exfiltration, or manipulation.

MitigationUpgrade ADAudit Plus to version 7271 or later to remediate the SQL injection vulnerability. Apply the latest vendor patch following standard change management procedures.

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. Confirm ADAudit Plus installation
    Locate the ADAudit Plus installation directory or check for the service running on the host (commonly installed in C:\ManageEngine\ADAudit Plus or /opt/ManageEngine/ADAudit Plus on Linux)
    Affected if ADAudit Plus is installed on the system
  2. Determine installed version and build number
    Check the product version - this is typically visible in the About section of the ADAudit Plus web console, in the installer filename, or in a version-info file within the installation directory
    Affected if The version is 7.2 (any build) or the build number is below 7271
  3. Verify file server auditing is enabled
    Check if file server auditing is configured in ADAudit Plus by reviewing the domain profile settings or agent configuration where file server audit policies are defined
    Affected if File server auditing profiles are active and collecting data from file servers
  4. Identify file server details feature usage
    Access the ADAudit Plus console and navigate to the File Server reports section to see if the file server details functionality is being queried or displayed
    Affected if File server details reports are being accessed or scheduled for generation

You are affected if ADAudit Plus version 7.2 (any build) or versions below 7.2 are installed AND file server auditing features are enabled in the environment.

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 ADAudit Plus to version 7271 or later to remediate the SQL injection vulnerability. Apply the latest vendor patch following standard change management procedures.

Recommended fix Moderate confidence

ADAudit Plus version 7.2 with build 7271 or later (verify exact build from ManageEngine)

  1. Contact ManageEngine support or visit the official ManageEngine ADAudit Plus download page to obtain the latest patched version
  2. Verify the exact build number (7271 or higher) of the available fix
  3. Backup your current ADAudit Plus installation and database before upgrading
  4. Apply the upgrade following ManageEngine's standard upgrade documentation
  5. After upgrading, confirm the SQL injection vulnerability is resolved by verifying file server audit functionality
Caveat Review ManageEngine upgrade documentation for any configuration or compatibility considerations before applying

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

Fix this in Manageengine Adaudit Plus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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