CVE-2026-42366
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 · uneditedMultiple reflected cross-site scripting (xss) vulnerabilities exist in the Web Interface / ssi.cgi functionality of GeoVision LPC2011/LPC2211 1.10. A specially crafted malicious url can lead to an arbitrary javascript code execution. An attacker can provide a crafted URL to trigger this vulnerability.
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 confidenceMultiple reflected cross-site scripting (XSS) vulnerabilities exist in the ssi.cgi web interface component of GeoVision LPC2011/LPC2211 version 1.10. Attackers can embed malicious JavaScript in crafted URLs that are reflected back by the server without proper sanitization, allowing arbitrary script execution in user browsers.
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= 1.10= 1.10CVSS 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.
-
Identify the GeoVision device modelAccess the device web interface or check the device documentation/label to confirm it is an LPC2011 or LPCVC2211 model.Affected if The device is not an LPC2011 or LPC2211 model.
-
Check the firmware versionLog into the device web interface and navigate to the system status or firmware information page to view the installed firmware version. Alternatively, check via SNMP or the device configuration backup.Affected if The firmware version is 1.10 exactly.
-
Verify the ssi.cgi endpoint is accessibleAttempt to access the ssi.cgi script via HTTP or HTTPS using the device IP address (for example: http://[device-ip]/cgi-bin/ssi.cgi). Check if the endpoint responds.Affected if The ssi.cgi endpoint returns a response and is reachable.
-
Test for reflected XSS in ssi.cgi parametersSend a crafted request to ssi.cgi with a test parameter value containing a benign string such as 'testxss123' and observe whether the response reflects this value back in the HTML output without encoding.Affected if User-supplied input is reflected in the response without proper HTML encoding.
-
Confirm web interface is exposedDetermine if the web interface is accessible from the network where the check is performed. Verify the HTTP/HTTPS service is listening on the device.Affected if The web interface is accessible and the device is reachable on the network.
The environment is affected if it uses a GeoVision LPC2011 or LPC2211 device running firmware version 1.10 with the ssi.cgi web interface accessible and reflecting unencoded user input back to the browser.
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 robust input validation and output encoding on the ssi.cgi endpoint to neutralize script injection attempts; if a firmware patch is available from GeoVision, apply it. Consider restricting web interface access to trusted networks or disabling it if unused.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42366 — 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-2026-42366 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