dbcve.org
Manageengine Adaudit PlusApplication · Zohocorp

CVE-2025-36527

HIGH · 8.3 CVSS v3.1 Published 2025-05-23
Fix available
A fix is available. Upgrade to 8.5 or later.
See remediation →
89/100
Remediation priority · High
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
Zohocorp ManageEngine ADAudit Plus versions below 8511 are vulnerable to SQL injection while exporting reports.

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 · moderate confidence

ManageEngine ADAudit Plus versions prior to 8511 contain a SQL injection vulnerability in the report export functionality. An attacker could inject malicious SQL queries through the export feature to manipulate database queries, potentially exfiltrating, modifying, or deleting sensitive audit data.

MitigationUpgrade ADAudit Plus to version 8511 or later. As a temporary control, restrict access to the report export functionality to authorized administrators only until the upgrade can be performed.

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:< 8.5= 8.5

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
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

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 installed version
    Locate the version information for your ADAudit Plus installation (typically accessible via the product's about page, installation directory, or admin console)
    Affected if The installed version is 8.5 or any version prior to 8.5 (versions 8.5 and below are affected)
  2. Confirm report export functionality is in use
    Determine whether the report export feature has been configured or is accessible within your ADAudit Plus environment
    Affected if Report export functionality is enabled and accessible to users in your environment
  3. Review access controls on export feature
    Examine user roles and permissions to determine which users or groups can access the report export functionality
    Affected if Users other than fully trusted administrators can access or trigger report exports
  4. Inspect audit and access logs for export-related requests
    Search logs for report export operations, looking for unusual SQL syntax, unexpected characters, or patterns indicative of injection attempts
    Affected if Suspicious SQL-like patterns appear in export request logs or database query logs
  5. Compare your version against the affected range
    Verify that your installed version falls within the affected range: versions less than 8.5 or exactly version 8.5
    Affected if Your version is 8.5 or below (prior to the 8511 patch release)

You are affected if ADAudit Plus version 8.5 or below is running AND the report export feature is accessible to users in your 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 8.5 or later
Fixed in 8.5
Interim mitigation

Upgrade ADAudit Plus to version 8511 or later. As a temporary control, restrict access to the report export functionality to authorized administrators only until the upgrade can be performed.

Recommended fix High confidence

ManageEngine AdAudit Plus 8.5.11 or later

  1. 1. Back up the existing ManageEngine AdAudit Plus configuration and database before upgrading
  2. 2. Stop the AdAudit Plus service
  3. 3. Download ManageEngine AdAudit Plus version 8.5.11 or later from the official ManageEngine website (www.manageengine.com)
  4. 4. Install or upgrade to the fixed version (8.5.11 or later)
  5. 5. Start the AdAudit Plus service
  6. 6. Verify the SQL injection vulnerability is remediated by testing the report export 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
  • Implementation6.0 h
  • Testing12.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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