CVE-2025-3833
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 ADSelfService Plus versions 6513 and prior are vulnerable to authenticated SQL injection in the MFA 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 confidenceADSelfService Plus versions 6513 and prior contain an authenticated SQL injection vulnerability in the MFA reports module. An attacker with valid authentication credentials can inject malicious SQL statements through the MFA reports functionality, potentially allowing unauthorized database access, data exfiltration, or manipulation.
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< 6.5= 6.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
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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.
-
Identify installed ADSelfService Plus versionAccess the ADSelfService Plus admin console and navigate to Admin > Product Overview, or check the version.txt file in the installation directory. Alternatively, check the build number shown in the login page footer or the About section.Affected if The version displayed is 6513 or lower, or the build number is below 6514.
-
Verify MFA reports module is enabledIn the admin console, go to Configuration > Self-Service Settings > MFA Settings and check if the MFA reports feature is configured and enabled for user access.Affected if MFA reports module is actively enabled and accessible to users.
-
Confirm authentication is configuredCheck that local/internal authentication, LDAP, or AD integration is enabled in Configuration > Authentication. Verify that user accounts exist with valid login credentials.Affected if Authentication is enabled and valid user accounts can log in to access the MFA reports functionality.
-
Review database query logs for suspicious patternsEnable and review database audit logs if available, or check the application logs (in the logs folder of the installation directory) for SQL statements that may contain injection payloads in MFA reports parameters.Affected if Logs show unusual SQL syntax or unexpected database queries originating from MFA reports module requests.
You are affected if ADSelfService Plus version is 6513 or prior, the MFA reports module is enabled, and valid authentication credentials can be used to access it.
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 · scoped6.5
Upgrade ADSelfService Plus to version 6514 or later. Until upgrade is possible, implement strict access controls and monitor database query logs for anomalous patterns.
Upgrade to ADSelfService Plus version 6.6 or later (the first version after 6.5 that addresses the authenticated SQL injection in MFA reports)
- 1. Identify current ADSelfService Plus version by navigating to the Admin/About section in the product interface
- 2. Download the latest version of ManageEngine ADSelfService Plus from the official vendor portal at www.manageengine.com
- 3. Review the release notes for the latest version to confirm it includes the SQL injection fix for CVE-2025-3833
- 4. Create a full backup of the ADSelfService Plus database and configuration files
- 5. Schedule a maintenance window as the upgrade will require service downtime
- 6. Stop the ADSelfService Plus service before beginning the upgrade
- 7. Install the upgraded version (version 6.6 or later which contains the security fix)
- 8. Restart the ADSelfService Plus service after successful installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3833 — 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-3833 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