CVE-2023-30353
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 · uneditedShenzen Tenda Technology IP Camera CP3 V11.10.00.2211041355 allows unauthenticated remote code execution via an XML document.
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 confidenceThe Tenda IP Camera CP3 version V11.10.00.2211041355 contains an unauthenticated remote code execution vulnerability. Attackers can execute arbitrary code by submitting a specially crafted XML document to the affected device, likely through a parsing flaw in XML processing.
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= 11.10.00.2211041355CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 network discovery/UPnP responses for 'CP3' or 'Tenda' in the device description or hostnameAffected if The device is not a Tenda CP3 camera - if it is CP3, proceed to next check
-
Determine the firmware versionLog into the camera's web interface and navigate to System Settings > Device Info, or query the device's /cgi-bin/login.cgi endpoint for version informationAffected if The firmware version displayed is exactly 11.10.00.2211041355 - if different, the specific vulnerability may not apply
-
Verify the web service is accessibleAttempt to access the camera's HTTP port (typically 80 or 8080) from the network. Check if the XML parsing endpoint responds to HTTP POST requestsAffected if The web interface is exposed and accepts unauthenticated requests to the XML processing endpoint - the vulnerability can be exploited if the service is reachable
-
Check for recent device activityReview network logs or firewall logs for unusual XML-formatted HTTP POST requests to the camera's IP address from untrusted sourcesAffected if There are incoming POST requests to the camera that contain XML payload data, indicating active exploitation attempts
You are affected if you have a Tenda CP3 camera running firmware version 11.10.00.2211041355 with its web interface accessible on the 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 dataIsolate the affected camera from untrusted networks immediately using network segmentation. Contact Tenda for available firmware patches; if no patch exists, consider replacing the device with a supported model.
- 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-30353 — 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-30353 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