CVE-2016-2305
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 · uneditedCross-site scripting (XSS) vulnerability in Ecava IntegraXor before 5.0 build 4522 allows remote attackers to inject arbitrary web script or HTML via a crafted URL.
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 confidenceCross-site scripting (XSS) vulnerability in Ecava IntegraXor SCADA web interface allows remote attackers to inject arbitrary JavaScript or HTML via crafted URLs before version 5.0 build 4522.
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<= 4.2.4502CVSS 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.
-
Identify if Ecava IntegraXor is installedCheck the Windows Programs and Features list, or look for the IntegraXor installation directory (typically in C:\Program Files\Ecava\IntegraXor or C:\IntegraXor)Affected if The software is present on the system
-
Determine the installed versionLocate the IntegraXor executable or check the version information file in the installation directory. Right-click the main executable and select Properties > Details to view the File VersionAffected if The version displayed is 4.2.4502 or lower, or if the version cannot be determined but is known to be from the 4.x branch before version 5.0 build 4522
-
Verify the build numberCheck the build number displayed in the IntegraXor application interface or in the version details of the executableAffected if The build number is 4502 or lower, indicating a version before the fix in build 4522
-
Confirm web interface is accessibleAttempt to access the IntegraXor web interface via a browser using the configured HTTP port (default port 8080), such as http://localhost:8080 or the assigned IP/hostnameAffected if The web interface is accessible and the version is confirmed as 4.2.4502 or lower
A system is affected if Ecava IntegraXor version 4.2.4502 or lower is installed and the web interface is accessible, since the XSS vulnerability exists in these versions before the fix in build 4522.
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 dataUpgrade to IntegraXor version 5.0 build 4522 or later; implement proper input validation and output encoding on all user-supplied parameters in the web application.
- 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-2016-2305 — 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-2016-2305 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