CVE-2025-5366
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 Exchange reporter Plus version 5722 and below are vulnerable to Stored XSS in the Folder-wise read mails with subject 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 confidenceA stored cross-site scripting (XSS) vulnerability exists in the Folder-wise read mails with subject report feature of ManageEngine Exchange Reporter Plus version 5722 and below. Attackers can inject malicious JavaScript payloads into the report parameters, which persist on the server and execute when administrators or users view the affected report, potentially leading to session hijacking or credential theft.
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< 5.7= 5.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Exchange Reporter Plus versionLocate the product version information in the administration console under Help > About, or check the build number in the installation directory or product release notesAffected if The installed version is 5.7 or below (build 5722 or lower)
-
Confirm Folder-wise read mails report feature existsNavigate to the Reports section in the Exchange Reporter Plus console and look for a report named 'Folder-wise read mails with subject' or similar in the mail traffic or audit reports sectionAffected if The report feature is present and accessible in the product interface
-
Inspect report configuration for injected scriptsAccess the configuration or settings for the Folder-wise read mails report and examine any customizable parameters such as subject filters, folder selections, or display options for unexpected script tags, encoded characters, or JavaScript event handlersAffected if The report parameters contain script tags, javascript: URIs, or other XSS vectors in fields like subject, folder name, or display name
-
Review saved report definitionsCheck the product's database or configuration files where report definitions are stored, looking for any stored XSS payloads in fields associated with the Folder-wise read mails reportAffected if Malicious JavaScript code or HTML tags are found persisted in the report configuration data
A user is affected if Exchange Reporter Plus version 5.7 or below is installed AND the Folder-wise read mails report feature contains injected XSS payloads in its parameters or configuration
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 · scoped5.7
Upgrade to a version higher than 5722 once available, or apply vendor-supplied patches. Additionally, implement proper input validation and output encoding for the Folder-wise read mails report to neutralize XSS vectors.
Exchange Reporter Plus version 5.8 or later
- 1. Back up your current Exchange Reporter Plus installation and database.
- 2. Download the latest version of ManageEngine Exchange Reporter Plus from the official ManageEngine website (www.manageengine.com).
- 3. Ensure version 5.8 or higher is selected for download, as versions 5.7 and below contain the stored XSS vulnerability.
- 4. Follow the standard upgrade procedure: stop the Exchange Reporter Plus service, run the installer, and follow the on-screen prompts.
- 5. After upgrade, verify the 'Folder-wise read mails with subject' report functionality works correctly.
- 6. Confirm the upgrade was successful by checking the version number in the product UI or about page.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5366 — 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-5366 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