dbcve.org
Manageengine Exchange Reporter PlusApplication · Zohocorp

CVE-2024-6204

HIGH · 8.1 CVSS v3.1 Published 2024-08-30
Fix available
A fix is available. Upgrade to 5.7 or later.
See remediation →
87/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 Exchange Reporter Plus versions before 5715 are vulnerable to SQL Injection in the reports 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 · moderate confidence

SQL Injection vulnerability in the reports module of ManageEngine Exchange Reporter Plus versions prior to 5715 allows attackers to inject malicious SQL queries through unsanitized input in the reporting functionality.

MitigationUpgrade ManageEngine Exchange Reporter Plus to version 5715 or later to patch the SQL injection vulnerability.

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
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 checks

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

  1. Locate Exchange Reporter Plus installation
    Check common installation directories such as C:\ManageEngine\ExchangeReporterPlus on Windows or /opt/ManageEngine/ExchangeReporterPlus on Linux. Look for the product's start.bat, start.sh, or the main application executable.
    Affected if The product is not installed on the system.
  2. Identify installed version
    In the installation directory, open the version.txt or build.txt file typically found in the conf or root folder. Alternatively, check the application banner when starting the service or look in the Windows Registry under HKLM\SOFTWARE\ManageEngine\ExchangeReporterPlus for the Version key.
    Affected if Unable to retrieve a version number from the installation.
  3. Compare version against vulnerable range
    Compare your installed version to the affected ranges: versions prior to 5.7 and version 5.7 exactly are vulnerable. Version 5715 and later are patched. For example, version 5714 or 5.6.2 would be in the vulnerable range.
    Affected if The installed version is less than 5715 (such as 5714, 5700, or any 5.x version prior to 5.7) or equals exactly 5.7.
  4. Verify reports module accessibility
    If the application is running, attempt to access the reports module via the web interface at /reports or check if the reports functionality is enabled in the application's administration console under Module Configuration.
    Affected if The reports module is accessible and the application version falls within the vulnerable range.

You are affected if ManageEngine Exchange Reporter Plus is installed with a version less than 5715 (including version 5.7) and the reports module is accessible.

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

Upgrade ManageEngine Exchange Reporter Plus to version 5715 or later to patch the SQL injection vulnerability.

Recommended fix High confidence

5715 or later

  1. 1. Back up the current Exchange Reporter Plus installation and its database before proceeding with any upgrade.
  2. 2. Download version 5715 or later of ManageEngine Exchange Reporter Plus from the official ManageEngine website (www.manageengine.com).
  3. 3. Follow the standard ManageEngine upgrade procedure for Exchange Reporter Plus, ensuring the upgrade is applied to the existing installation.
  4. 4. After upgrade completion, verify the SQL injection vulnerability in the reports module is no longer present.
  5. 5. Confirm normal functionality of the reporting module works as expected.

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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