CVE-2023-22370
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 · uneditedStored cross-site scripting vulnerability in Wired/Wireless LAN Pan/Tilt Network Camera CS-WMV02G all versions allows a network-adjacent authenticated attacker to inject an arbitrary script. NOTE: This vulnerability only affects products that are no longer supported by the developer.
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 confidenceStored cross-site scripting (XSS) vulnerability in the CS-WMV02G network camera web interface allows an authenticated, network-adjacent attacker to inject malicious scripts that persist and execute when other users access the affected functionality. The attack requires valid credentials and local network access, limiting exploitation scope.
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 dataall versionsCVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:A/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 device modelAccess the camera's web interface or check physical device labeling for model number CS-WMV02G or Planex. If using a network scan, look for devices responding with 'CS-WMV02G' in HTTP headers or device info.Affected if Device is a Planex CS-WMV02G network camera (all versions are affected)
-
Confirm web interface is enabledAttempt to access the camera's web interface via HTTP/HTTPS on common ports (80, 443, 8080). If the login page loads, the web interface is active.Affected if Web interface is accessible and responds to HTTP requests
-
Verify authentication is configuredCheck if the camera requires valid credentials to access the web interface. Attempt a login with any known credentials or check if default credentials are in use.Affected if Valid credentials exist and grant access to the web interface (authentication is the exploitation prerequisite)
-
Assess network accessibilityDetermine if the camera web interface is accessible from beyond the local network segment. Check firewall rules, NAT configurations, or port forwarding that expose the camera to wider networks.Affected if Camera web interface is reachable from network segments outside the trusted local network
-
Inspect for suspicious stored contentLog into the web interface and review any user-editable fields such as device name, description, or configuration parameters. Look for unexpected script tags, JavaScript URLs, or encoded payloads in stored values.Affected if Unexpected script tags or JavaScript content exists in camera configuration fields (indicates potential exploitation)
You are affected if you have a Planex CS-WMV02G camera with its web interface enabled and accessible to authenticated users on your network.
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 dataSince the product is end-of-life and unsupported, pursue device replacement with a currently supported model or implement compensating controls such as network segmentation, web application firewall rules, and disabling the camera's web interface if not required.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.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 $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22370 — 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-2023-22370 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