CVE-2017-17698
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 · uneditedZoho ManageEngine Password Manager Pro 9 before 9.4 (9400) has reflected XSS in SearchResult.ec and BulkAccessControlView.ec.
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 confidenceReflected Cross-Site Scripting (XSS) vulnerability in Zoho ManageEngine Password Manager Pro versions before 9.4 (9400). The vulnerability exists in the SearchResult.ec and BulkAccessControlView.ec endpoints, where user-supplied input is reflected back without proper sanitization, allowing execution of malicious JavaScript in the context of the victim's browser.
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>= 9.0, < 9.4CVSS 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.0/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.
-
Check installed Password Manager Pro versionLog into the Password Manager Pro admin console and navigate to the About or Version section, typically found under the Help menu or administration settingsAffected if version is 9.0 through 9.3.x (builds before 9400)
-
Confirm version is in vulnerable rangeVerify that the installed version meets both conditions: greater than or equal to 9.0 AND less than 9.4 (9400)Affected if version falls within 9.0 <= version < 9.4
-
Test SearchResult.ec endpoint for reflected inputSend an HTTP GET request to the SearchResult.ec endpoint with a test parameter containing a benign string (such as 'test123') and observe if the same value appears unmodified in the responseAffected if the submitted input is reflected back in the page without sanitization or encoding
-
Test BulkAccessControlView.ec endpoint for reflected inputSend an HTTP GET request to the BulkAccessControlView.ec endpoint with a test parameter containing a benign string and examine whether the response reflects the input unchangedAffected if the submitted input is reflected back in the page without sanitization or encoding
You are affected if Password Manager Pro version is 9.0 through 9.3.x AND the SearchResult.ec or BulkAccessControlView.ec endpoints are accessible and reflect user input without encoding.
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 data9.4
Upgrade Password Manager Pro to version 9.4 (9400) or later. Until then, disable or restrict access to the affected endpoints and implement WAF rules to filter malicious request patterns.
- Consultation2.0 h
- Implementation3.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 $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17698 — 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-2017-17698 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