CVE-2025-36528
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 · uneditedZohocorp ManageEngine ADAudit Plus versions 8510 and prior are vulnerable to authenticated SQL injection in Service Account Auditing 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 · high confidenceManageEngine ADAudit Plus versions 8510 and prior contains an authenticated SQL injection vulnerability in the Service Account Auditing reports module. An attacker with valid credentials can inject malicious SQL queries through this functionality to potentially exfiltrate, modify, or delete database contents.
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< 8.5= 8.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm ManageEngine ADAudit Plus is installedLocate the ADAudit Plus installation directory (commonly C:\Program Files\ManageEngine\ADAudit Plus or /opt/ManageEngine/ADAudit Plus) and check for the product. Alternatively, check running services for 'ADAudit Plus' service.Affected if The product is installed on the system
-
Identify the installed ADAudit Plus versionCheck the version by opening the ADAudit Plus web UI and viewing the About/Help section, or check the build number in the installation directory (typically in a version.txt or build.properties file). Compare against the affected range: versions less than 8.5 or exactly version 8.5 (build 8510 and prior).Affected if The installed version is 8.5 or any version below 8.5 (such as 8.4, 8.3, etc.)
-
Determine if Service Account Auditing module is configuredIn the ADAudit Plus web interface, navigate to the Reports section and check whether Service Account Auditing reports are available or enabled. This module is typically found under the 'IT Compliance' or 'Auditing' categories in the report navigation.Affected if The Service Account Auditing reports module is present and accessible in the reports section
-
Check for SQL injection indicators in audit or database logsReview ADAudit Plus database logs and web access logs for suspicious SQL syntax patterns within report parameters, especially in requests related to Service Account Auditing. Look for unusual characters like quotes, UNION, SELECT, or DROP in parameter values.Affected if Unusual SQL-like patterns appear in logs for Service Account Auditing report requests
You are affected if ManageEngine ADAudit Plus is installed with version 8.5 or any version prior to 8.5 and the Service Account Auditing reports module is accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped8.5
Upgrade ManageEngine ADAudit Plus to a version beyond 8510, or apply vendor-provided patches. If immediate patching is not possible, restrict access to the Service Account Auditing reports to trusted administrators only and implement Web Application Firewall (WAF) rules to detect and block SQL injection attempts.
Upgrade to a version higher than 8.5 (or 8510) - obtain the latest stable release from ManageEngine
- 1. Back up the current ADAudit Plus installation, including the database and configuration files.
- 2. Download the latest version of ManageEngine ADAudit Plus from the official ManageEngine website (www.manageengine.com).
- 3. Stop the ADAudit Plus service before upgrading.
- 4. Install the latest version, ensuring to preserve existing configurations when prompted.
- 5. Start the ADAudit Plus service after installation completes.
- 6. Verify the upgrade by logging into the administration console and checking the version number.
- 7. Test the Service Account Auditing reports functionality to confirm the SQL injection vulnerability is resolved.
- 8. Review and monitor logs for any unusual database query patterns.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36528 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-36528 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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