CVE-2021-41288
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 · uneditedZoho ManageEngine OpManager version 125466 and below is vulnerable to SQL Injection in the getReportData API.
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 confidenceZoho ManageEngine OpManager versions 125466 and below contain a SQL Injection vulnerability in the getReportData API. Attackers can inject malicious SQL queries through this API endpoint to manipulate database queries, potentially allowing unauthorized data access, modification, or deletion.
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<= 12.4= 12.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify OpManager installation versionAccess the OpManager web UI and navigate to the About or Help section, typically found in the top-right menu or at /jsp/About.jsp. Alternatively, check the install directory for a version file or check the build number displayed on the login page.Affected if The displayed version is 12.4 or lower, or exactly version 12.5, or the build number is 125466 or below.
-
Locate the getReportData API endpointVerify the API endpoint exists by attempting to access it at the typical path: /api/json/anonymous/getReportData or /api/getReportData. Check web server access logs for any existing requests to this endpoint.Affected if The endpoint is accessible and responds to requests without authentication errors.
-
Confirm API accessibilitySend a test HTTP request to the getReportData endpoint using a tool like curl or Burp Suite. Inspect whether the endpoint accepts parameters without proper input validation or authentication checks.Affected if The endpoint accepts user-supplied parameters and returns database query results without requiring valid SQL input sanitization.
You are affected if your installed ManageEngine OpManager version is 12.4 or lower, equals 12.5, or has a build number of 125466 or below, and the getReportData API endpoint is accessible and accepts unsanitized input.
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.
From vendor dataUpgrade ManageEngine OpManager to a version above 125466 that includes the security patch for this SQL injection vulnerability. If immediate patching is not possible, implement web application firewall (WAF) rules to filter malicious SQL payloads in requests to the getReportData endpoint.
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-41288 — 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-2021-41288 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