CVE-2025-7632
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 5723 and below are vulnerable to the Stored XSS Vulnerability in the Public Folders 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 confidenceManageEngine Exchange Reporter Plus versions 5723 and below contains a stored Cross-Site Scripting (XSS) vulnerability in the Public Folders report feature. Attackers can inject malicious JavaScript payloads into the Public Folders report data that persists and executes in the browsers of users who view the affected report.
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.6= 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.
-
Identify the installed Exchange Reporter Plus versionAccess the product's About or System Settings page in the admin console, or check the version information file in the product installation directoryAffected if The version is 5723 or below, specifically versions 5.6 or 5.7 (or any build number less than 5723)
-
Confirm the Public Folders report feature is enabledNavigate to the Reports section in the admin interface and verify if the Public Folders report module is accessible or enabled for usersAffected if The Public Folders report feature is available and users have permission to view it
-
Inspect Public Folders report data for injected scriptsView the Public Folders report and examine the displayed data fields (folder names, paths, metadata) for any suspicious script tags, event handlers, or encoded payloadsAffected if The report displays unsanitized content containing script tags or JavaScript event attributes like onload, onerror, or onmouseover
-
Review browser security logs or consoleOpen a browser's developer console while viewing the Public Folders report and check for any JavaScript errors or executed scriptsAffected if Unexpected JavaScript executes or errors appear related to the report's content
A user is affected if they are running Exchange Reporter Plus version 5723 or below AND the Public Folders report feature is accessible, with any stored XSS payloads present in the report data that could execute in browsers.
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 · scopedUpgrade to a version above 5723 when available. Until then, implement output encoding and input validation on the Public Folders report functionality, and consider restricting access to the affected report.
Latest available version of Exchange Reporter Plus (check www.manageengine.com for the specific fixed release)
- 1. Back up your current ManageEngine Exchange Reporter Plus installation and configuration.
- 2. Visit the official ManageEngine download page for Exchange Reporter Plus at www.manageengine.com to obtain the latest version.
- 3. Download the most recent version of Exchange Reporter Plus available.
- 4. Stop the Exchange Reporter Plus service before applying the upgrade.
- 5. Install the new version following the standard upgrade procedure in the product documentation.
- 6. Start the Exchange Reporter Plus service after installation completes.
- 7. Verify that the Public Folders report functionality is working correctly.
- 8. Test that the XSS vulnerability is remediated by attempting to inject script content in the Public Folders report fields.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7632 — 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-7632 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