CVE-2025-7633
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 Custom 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 confidenceStored XSS vulnerability in the Custom report feature of ManageEngine Exchange Reporter Plus (versions 5723 and below) allows attackers to inject malicious JavaScript that persists on the server and executes in the browsers of users who view the affected 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.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 installationLocate the ManageEngine Exchange Reporter Plus installation directory (commonly C:\Program Files\ManageEngine\ExchangeReporterPlus or /opt/ManageEngine/ExchangeReporterPlus). Check for the presence of run.bat, start.bat, or corresponding shell scripts.Affected if The product is not installed on the system.
-
Check product versionAccess the product's About page via the admin console (typically at https://localhost:8181/about.html) or check the version.txt/build.properties file in the installation directory. Note the build/version number.Affected if The version is 5723 or below, or versions 5.6 and 5.7 as specified.
-
Verify Custom Reports feature is accessibleLog in to the Exchange Reporter Plus admin console and navigate to the Custom Reports section (usually under Reports > Custom Reports or similar). Confirm the feature is present and accessible.Affected if The Custom Reports feature exists and is accessible in the web interface.
-
Inspect existing Custom Reports for injected scriptsNavigate to the Custom Reports list in the admin console. Review each report name, description, and any configured parameters for suspicious script tags (<script>, javascript:, onerror=, onload=, etc.). Alternatively, query the database (typically PostgreSQL) tables storing report definitions for HTML/script content.Affected if Any Custom Report contains unencoded HTML, script tags, or JavaScript event handlers in report fields.
A user is affected if Exchange Reporter Plus version 5723 or below (or version 5.6/5.7) is installed AND the Custom Reports feature is accessible with potentially malicious script content stored in report definitions.
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.
From vendor dataApply output encoding and input validation/sanitization to the Custom report feature to neutralize injected scripts; upgrade to a patched version above 5723 if available from Zoho.
- 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-7633 — 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-7633 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