CVE-2017-11288
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 · uneditedAn issue was discovered in Adobe Connect 9.6.2 and earlier versions. A reflected cross-site scripting vulnerability exists that can result in information disclosure.
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 confidenceA reflected cross-site scripting (XSS) vulnerability in Adobe Connect 9.6.2 and earlier versions allows attackers to inject malicious scripts through unsanitized user input, potentially leading to session hijacking or information disclosure via cookie theft or credential harvesting.
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.6.2CVSS 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.
-
Verify Adobe Connect is installedCheck for Adobe Connect service or process running on the system. Common installation paths include C:\Program Files\Adobe\Adobe Connect\ on Windows or /opt/adobe-connect/ on Linux. Look for the 'Connect' service or executable.Affected if Adobe Connect software is present on the system
-
Determine installed Adobe Connect versionAccess the Adobe Connect About page typically found at /about/ relative to the Connect installation, or check version information in the installation directory. On Windows, also check Add/Remove Programs for the installed version.Affected if The installed version is 9.6.2 or any earlier version (9.x versions <= 9.6.2)
-
Identify accessible web endpointsReview the Adobe Connect web application's accessible URLs and parameters. The vulnerability affects endpoints that process user-supplied input without proper sanitization.Affected if The web interface is exposed and accessible to users or attackers
-
Check for reflected input parametersInspect web requests to Adobe Connect endpoints. Look for parameters in URLs or POST data that reflect user input back in the response without encoding. Common areas include login forms, search functions, or URL-based parameters.Affected if User-supplied parameters are reflected in server responses without sanitization
-
Verify XSS protection mechanismsInspect HTTP response headers for security controls like Content-Security-Policy (CSP) with XSS protections, X-XSS-Protection header, or HttpOnly flags on session cookies. Also review application-level output encoding practices.Affected if No XSS protection headers are present and application does not encode reflected user input
The environment is affected if Adobe Connect version 9.6.2 or earlier is installed and the web interface with unsanitized user input parameters is accessible.
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 dataImplement proper input validation and output encoding on all user-supplied parameters in the affected endpoint. Additionally, deploy Content-Security-Policy headers to mitigate XSS execution.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11288 — 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-11288 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