CVE-2021-23854
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 · uneditedAn error in the handling of a page parameter in Bosch IP cameras may lead to a reflected cross site scripting (XSS) in the web-based interface. This issue only affects versions 7.7x and 7.6x. All other versions are not affected.
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 reflected cross-site scripting vulnerability exists in the web interface of Bosch IP cameras versions 7.7x and 7.6x. The issue stems from improper handling of a page parameter, allowing attackers to inject malicious scripts through the URL that execute in the context of a victim's browser session.
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= 7.62= 7.70= 7.72= 7.62= 7.70= 7.72= 7.62= 7.70= 7.72= 7.75= 7.76CVSS 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 camera firmware platformAccess the camera web interface or use ONVIF/SSH to determine if the device uses Cpp6, Cpp7, Cpp7.3, or Cpp13 firmware platform. This is typically visible in the system information or firmware details page.Affected if The camera runs on Bosch Cpp6, Cpp7, Cpp7.3, or Cpp13 firmware platform.
-
Check installed firmware versionNavigate to the camera web interface System Overview or firmware information page. Alternatively, use the camera's API or SSH access to retrieve the exact firmware version number.Affected if The firmware version is exactly 7.62, 7.70, 7.72 (for Cpp6/Cpp7/Cpp7.3) or exactly 7.75, 7.76 (for Cpp13).
-
Verify web interface is enabledConfirm the camera's web interface (HTTP/HTTPS) is currently accessible and enabled in the network configuration.Affected if The web interface is enabled and reachable on the network.
-
Inspect URL parameter handlingTest the web interface by requesting a page with a crafted 'page' parameter in the URL (for example: /?page=<script>alert(1)</script>) and observe if the parameter value is reflected back in the response without proper encoding.Affected if The page parameter value is reflected in the HTML response without sanitization, indicating the XSS vulnerability is present.
The environment is affected if the Bosch IP camera runs Cpp6, Cpp7, Cpp7.3 firmware version 7.62/7.70/7.72 or Cpp13 firmware version 7.75/7.76, and the web interface is enabled and reflects the page parameter unsanitized in the response.
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 affected Bosch IP camera firmware to a patched version (all other versions are not affected). If immediate patching is not feasible, implement web application firewall rules to filter malicious page parameter payloads.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-23854 — 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-2021-23854 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