dbcve.org
Manageengine Adaudit PlusApplication · Zohocorp

CVE-2023-49333

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 dashboard graph feature.

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 dashboard graph feature of Zoho ManageEngine ADAudit Plus versions prior to 7271 allows authenticated attackers to inject malicious SQL queries through unsanitized input, potentially enabling data exfiltration, manipulation, or privilege escalation within the database.

MitigationUpgrade ADAudit Plus to version 7271 or later to remediate the SQL injection vulnerability. Prior to upgrade, ensure current backups exist and schedule during maintenance window.

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 ADAudit Plus version
    Access the ADAudit Plus Admin Console and navigate to the About section, typically found under Help > About or Settings > Product Information. Alternatively, check the startup logs or the installer properties file in the installation directory.
    Affected if Installed version is 7.2 or any version below 7.2 (e.g., 7.1, 7.0, 6.x)
  2. Confirm dashboard graph feature is accessible
    Verify that the dashboard/graph feature is enabled in ADAudit Plus. This is typically found in the main dashboard view where graph widgets display audit data. Check if the user role has access to dashboard visualizations.
    Affected if Dashboard graph feature is enabled and accessible to authenticated users
  3. Verify authentication configuration
    Check the configured authentication methods in ADAudit Plus under Settings > Authentication. Determine if local users, domain users, or external authentication sources are enabled.
    Affected if At least one authentication method is configured allowing user access to the application
  4. Confirm the build number
    Locate the full build number in the About section or startup logs. The affected version 7.2 corresponds to builds prior to 7271. Compare your build number against 7271.
    Affected if Build number is less than 7271

You are affected if your ADAudit Plus installation is version 7.2 or any version below 7.2 (build < 7271), and authenticated users have access to the dashboard graph feature.

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. Prior to upgrade, ensure current backups exist and schedule during maintenance window.

Recommended fix Moderate confidence

ADAudit Plus build 7271 or later (or latest stable release)

  1. Log into ManageEngine ADAudit Plus as an administrator
  2. Navigate to the Admin or Settings section
  3. Look for the 'Check for Updates' or 'Upgrade' option
  4. Download and apply the update to build 7271 or later
  5. Alternatively, download the latest version from the official ManageEngine website (www.manageengine.com/products/adaudit-plus/)
  6. After upgrading, verify the dashboard graph feature is functioning correctly
  7. Confirm the SQL injection vulnerability is resolved by testing the affected dashboard graph functionality

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

Fix this in Manageengine Adaudit Plus Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49333 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-49333 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