CVE-2018-7827
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 · uneditedA Cross-Site Scripting (XSS) vulnerability exists in the 1st Gen. Pelco Sarix Enhanced Camera and Spectra Enhanced PTZ Camera which a remote attacker can execute arbitrary HTML and script code in a user’s browser session.
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 in the web interface of 1st Gen. Pelco Sarix Enhanced and Spectra Enhanced PTZ cameras allows a remote attacker to inject malicious HTML/script code that executes in the context of an authenticated user's browser session when viewing compromised content.
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>= 2.11>= 2.11>= 2.11>= 2.11< 2.2.3.0< 2.2.3.0< 2.2.3.0< 2.2.3.0CVSS 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.0/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.
-
Identify camera model and firmware versionAccess the camera's web interface or use SNMP/OID queries to retrieve the exact model number and current firmware version. This information is typically found in the system information or about page of the web interface.Affected if The firmware version falls within the affected ranges: D6220/D6220l/D6230/D6230l versions >= 2.11, or Imes19 (1i/1s/1p) and Ime119 1i versions < 2.2.3.0
-
Verify web interface is enabledConfirm that the camera's web interface HTTP/HTTPS service is active and accessible. Check network configuration or attempt to access the login page.Affected if The web interface is accessible and running, as this is required for the XSS to be triggered.
-
Inspect web interface input fields for injected scriptsLog into the camera web interface as an administrator and review all configurable fields where user input is stored, such as device names, descriptions, or custom labels. Look for any unexpected HTML script tags, javascript: URIs, or event handlers in these fields.Affected if Malicious script code is found stored in any user-configurable web interface field, indicating the stored XSS payload has been injected.
-
Review browser console for XSS errorsAccess the camera web interface using a web browser and open the developer console. Navigate through all configuration pages while observing console warnings or errors related to script execution.Affected if Unexpected script execution errors or warnings appear in the console, suggesting stored XSS payloads are present in the page.
You are affected if your camera model matches one of the listed products AND the firmware version is within the specified vulnerable ranges AND the web interface is enabled and 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 data2.2.3.0
Apply vendor firmware updates; if unavailable, restrict network access to camera management interfaces and implement input validation/output encoding at upstream proxies/WAFs.
- Consultation4.0 h
- Implementation2.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7827 — 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-2018-7827 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