CVE-2025-5347
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 versions before 5723 are vulnerable to Stored Cross Site Scripting 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 confidenceZohocorp ManageEngine Exchange Reporter Plus versions before 5723 contain a stored cross-site scripting (XSS) vulnerability in the reports module. Attackers can inject malicious JavaScript payloads into report content that persists on the server and executes when other users view those reports.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Confirm Exchange Reporter Plus is installedLocate the ManageEngine Exchange Reporter Plus installation in your environment - check for the product directory or running serviceAffected if Product is not installed means not affected
-
Check installed version numberAccess the product's about or version information page, typically found in the admin console or in the installation directoryAffected if Version is 5.7 or any version below 5.7 (for example 5.6, 5.5, etc.) - versions before 5723 are affected
-
Verify reports module is accessibleConfirm the reports module is enabled and accessible to users in your deploymentAffected if Reports module is in use - the XSS payload executes when users view malicious report content
-
Inspect existing reports for suspicious contentReview stored reports for unexpected script tags, javascript: URLs, or other XSS payloads in report fieldsAffected if Malicious JavaScript payloads are found embedded in report content - indicates active exploitation or testing
You are affected if Exchange Reporter Plus version 5.7 or any version below 5.7 is installed and the reports module is accessible to users.
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 version 5723 or later. Additionally, implement proper input validation and output encoding in the reports module to neutralize XSS vectors.
5723
- Back up the current Exchange Reporter Plus installation and configuration data
- Stop the Exchange Reporter Plus service
- Download version 5723 or later from the official ManageEngine website
- Install the upgrade following the standard ManageEngine upgrade procedure
- Start the Exchange Reporter Plus service
- Verify the application is running correctly and the reports module is accessible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5347 — 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-5347 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