dbcve.org
Manageengine Exchange Reporter PlusApplication · Zohocorp

CVE-2024-38872

HIGH · 8.8 CVSS v3.1 Published 2024-07-26
Fix available
A fix is available. Upgrade to 5.7 or later.
See remediation →
94/100
Remediation priority · Urgent
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 Exchange Reporter Plus versions 5717 and below are vulnerable to the authenticated SQL injection in the monitoring module.

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 Exchange Reporter Plus versions 5717 and below contains an authenticated SQL injection vulnerability in the monitoring module. An attacker with valid credentials can inject malicious SQL queries through input fields in the monitoring functionality, potentially allowing unauthorized database access, data exfiltration, or manipulation.

MitigationApply the vendor patch/upgrade to a version higher than 5717. If immediate patching is not possible, restrict access to the monitoring module to only trusted users and implement input validation and WAF rules as compensating controls.

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 Exchange Reporter PlusApplication
Affected:< 5.7= 5.7

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
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Exchange Reporter Plus installation
    Locate the ManageEngine Exchange Reporter Plus installation directory, typically under C:\Program Files\ManageEngine\ExchangeReporterPlus or /opt/ManageEngine/ExchangeReporterPlus on Linux
    Affected if The product is not installed on the system
  2. Identify installed version
    Access the product's About or Version section in the web interface (usually via Help > About) or check the build.info/version.txt file in the installation directory
    Affected if Unable to determine the version number
  3. Compare version to affected range
    Note the build number shown (for example, build 5717 corresponds to version 5.7). Check if the version is 5.7 with build <= 5717, or any version lower than 5.7
    Affected if Version is 5.7 with build 5717 or lower, or any version below 5.7
  4. Verify monitoring module accessibility
    Log into the product with valid credentials and navigate to the Monitoring module section in the web interface
    Affected if Monitoring module is accessible and accepts user input

If the installed version of Exchange Reporter Plus is 5.7 with build 5717 or lower, or any version below 5.7, and the monitoring module is accessible, the environment is affected by this SQL injection vulnerability.

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 5.7 or later
Fixed in 5.7
Interim mitigation

Apply the vendor patch/upgrade to a version higher than 5717. If immediate patching is not possible, restrict access to the monitoring module to only trusted users and implement input validation and WAF rules as compensating controls.

Recommended fix Moderate confidence

Upgrade to a version of Exchange Reporter Plus newer than 5.7 (check vendor for latest stable release)

  1. Verify current version of ManageEngine Exchange Reporter Plus by checking the product console or build number
  2. Take a complete backup of the Exchange Reporter Plus installation, including database and configuration files
  3. Download the latest version of ManageEngine Exchange Reporter Plus from the official vendor website (www.manageengine.com)
  4. Stop the Exchange Reporter Plus service before upgrading
  5. Install the new version following the vendor's upgrade documentation
  6. Start the Exchange Reporter Plus service after successful installation
  7. Verify the SQL injection vulnerability is resolved by confirming the monitoring module functions correctly
  8. Review audit logs to ensure no SQL injection exploitation occurred prior to the upgrade
Caveat Review release notes for any configuration or feature changes between 5.7 and the target version; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Manageengine Exchange Reporter Plus Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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