dbcve.org
Manageengine Exchange Reporter PlusApplication · Zohocorp

CVE-2025-5966

HIGH · 8.1 CVSS v3.1 Published 2025-06-26
Fix available
A fix is available. Upgrade to 5.7 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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 version 5722 and below are vulnerable to Stored XSS in the Attachments by filename keyword report.

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

Stored Cross-Site Scripting (XSS) vulnerability in Zohocorp ManageEngine Exchange Reporter Plus version 5722 and below. The vulnerability exists in the 'Attachments by filename keyword' report feature where malicious scripts can be injected via the filename keyword parameter and permanently stored, executing when users access the affected report.

MitigationUpdate ManageEngine Exchange Reporter Plus to a version newer than 5722. Until then, disable or restrict access to the Attachments by filename keyword report feature and implement output encoding for user-supplied filename data.

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Confirm Exchange Reporter Plus is installed
    Locate the installation directory (commonly C:\Program Files\ManageEngine\Exchange Reporter Plus on Windows or /opt/ManageEngine/ExchangeReporterPlus on Linux). Identify the product by the presence of run.bat, start.bat, or the ExchangeReporterPlus executable.
    Affected if The product is present on the system
  2. Determine the installed version
    Check the version by accessing the web interface Help > About page, or locate a version.txt, version.info, or build.info file in the installation directory. Note the build number (such as 5722) or version number (such as 5.7).
    Affected if Version is 5.7 or build 5722 or below
  3. Verify the Attachments by filename keyword report exists
    Log into the web console and navigate to Reports > Email Reports > Attachments. Locate the specific report named 'Attachments by filename keyword' or similar phrasing indicating filename keyword filtering.
    Affected if The report feature is present and accessible in the console
  4. Inspect filename keyword settings for XSS payloads
    Access the configuration or saved report settings for this specific report. Examine any configured filename keywords for suspicious patterns including <script>, javascript:, onload=, onerror=, img src=x onerror=, or other HTML/script tags that could indicate attempted exploitation.
    Affected if The filename keyword parameter contains any script tags, javascript: URIs, or event handler attributes

If Exchange Reporter Plus version 5.7 or build 5722 or below is installed AND the Attachments by filename keyword report is accessible AND malicious script payloads are found in the filename keyword configuration, the environment is affected by CVE-2025-5966.

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

Update ManageEngine Exchange Reporter Plus to a version newer than 5722. Until then, disable or restrict access to the Attachments by filename keyword report feature and implement output encoding for user-supplied filename data.

Recommended fix Moderate confidence

Latest version of ManageEngine Exchange Reporter Plus (version > 5.7 / build > 5722)

  1. 1. Back up the current ManageEngine Exchange Reporter Plus installation and its database
  2. 2. Download the latest version of ManageEngine Exchange Reporter Plus from the official vendor website (www.manageengine.com)
  3. 3. Stop the Exchange Reporter Plus service
  4. 4. Install the latest version following the vendor's upgrade documentation
  5. 5. Start the Exchange Reporter Plus service
  6. 6. Verify the XSS vulnerability is resolved by testing the 'Attachments by filename keyword' report functionality
Caveat Review vendor release notes for any configuration or feature changes between version 5.7 and the target upgrade version

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

Fix this in Manageengine Exchange Reporter Plus Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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