CVE-2026-4107
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 5802 are vulnerable to Stored XSS in Folder Message Count and Size 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 · high confidenceA stored Cross-Site Scripting (XSS) vulnerability exists in Zohocorp ManageEngine Exchange Reporter Plus versions prior to 5802. The vulnerability is located in the Folder Message Count and Size report feature, where malicious JavaScript payload can be injected and persistently stored, executing when other users view the 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.8= 5.8CVSS 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.
-
Verify Exchange Reporter Plus installationLocate the ManageEngine Exchange Reporter Plus installation directory, typically found under C:\Program Files\ManageEngine\ or /opt/ManageEngine/ on Windows and Linux systems respectively. Look for the product executable or service.Affected if The product is installed on the system
-
Determine installed versionCheck the product version through the administration console (typically accessible at https://localhost:8080 or the configured port), or look for a version file within the installation directory. Compare the version number against the affected range: versions before 5802 and version 5.8.Affected if The installed version is less than 5802 or equals 5.8
-
Check Folder Message Count and Size report accessLog into the Exchange Reporter Plus web interface with a valid user account and navigate to the reporting section. Look for the Folder Message Count and Size report feature under the available report types.Affected if This specific report feature exists and is accessible to authenticated users
-
Inspect the Folder Message Count and Size report for suspicious contentAccess the Folder Message Count and Size report and review all entries for unexpected or encoded JavaScript tags, script elements, or event handler attributes in fields that should contain numeric or text data.Affected if Malicious JavaScript payloads are present in the report data
A user is affected if their installed Exchange Reporter Plus version is below 5802 (or equals 5.8) and the Folder Message Count and Size report feature is accessible to authenticated users, particularly if the report contains unexpected script content.
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.8
Upgrade ManageEngine Exchange Reporter Plus to version 5802 or later to remediate this stored XSS vulnerability.
Version 5.8 Build 5802 or later
- Log in to ManageEngine Exchange Reporter Plus as an administrator
- Navigate to the Admin or Settings section of the application
- Locate the 'Check for Updates' or 'Upgrade' option
- Alternatively, download the latest version from the official ManageEngine downloads page: www.manageengine.com
- Ensure you back up the current configuration and database before upgrading
- Run the installer for version 5802 or later
- Follow the on-screen upgrade instructions
- After upgrade, verify the Folder Message Count and Size report functions correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4107 — 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-2026-4107 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