dbcve.org
Manageengine Adaudit PlusApplication · Zohocorp

CVE-2025-41407

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 in the OU History report.

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

ManageEngine ADAudit Plus versions prior to 8511 contain a SQL injection vulnerability in the OU History report feature. Attackers can inject malicious SQL queries through unsanitized user input in this report, potentially allowing unauthorized database access, data exfiltration, or manipulation of Active Directory audit data.

MitigationUpgrade ManageEngine ADAudit Plus to version 8511 or later. Additionally, implement input validation and parameterized queries as defense-in-depth while planning the upgrade.

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 the installed ADAudit Plus version
    Locate the ADAudit Plus installation directory and check the version.txt or version.ini file, or access the product's About page in the admin console
    Affected if The installed version is 8.5 or any version lower than 8.5 (e.g., 8.0, 7.x, 6.x)
  2. Confirm the OU History report module exists
    Navigate to the ADAudit Plus web interface and check if the OU History report option is visible under the Active Directory Auditing reports section
    Affected if The OU History report feature is present and accessible in the product interface
  3. Verify web server accessibility and authentication
    Check if the ADAudit Plus web portal is exposed to the network and whether it requires strong authentication for access
    Affected if The web interface is accessible without multi-factor authentication or from untrusted networks
  4. Review audit logs for SQL injection indicators
    Examine ADAudit Plus logs (located in the product logs directory) and Windows Event Viewer for unusual query patterns or SQL syntax errors related to OU History reports
    Affected if Log entries show malformed SQL queries or unauthorized database access attempts through the OU History endpoint

A user is affected if ADAudit Plus version 8.5 or lower is running and the OU History report feature is accessible to unauthorized or weakly authenticated users.

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 ManageEngine ADAudit Plus to version 8511 or later. Additionally, implement input validation and parameterized queries as defense-in-depth while planning the upgrade.

Recommended fix Moderate confidence

8511 or higher

  1. 1. Back up the current ADAudit Plus installation and database before upgrading.
  2. 2. Download ADAudit Plus version 8511 or higher from the official ManageEngine website.
  3. 3. Stop the ADAudit Plus service before proceeding with the upgrade.
  4. 4. Run the installer for the new version, following the on-screen prompts.
  5. 5. After installation, start the ADAudit Plus service.
  6. 6. Verify the OU History report functionality is working correctly.
  7. 7. Confirm the version upgrade was successful by checking the build number in the About section.
Caveat Standard minor version upgrade; review release notes for any configuration or feature changes

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
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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