dbcve.org
Sitemanager 1129 FirmwareOperating system · Secomea

CVE-2021-32005

MEDIUM · 5.4 CVSS v3.1 Published 2022-03-10
Fix available
A fix is available. Upgrade to 9.6.621421014 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Cross-site Scripting (XSS) vulnerability in log view of Secomea SiteManager allows a logged in user to store javascript for later execution. This issue affects: Secomea SiteManager Version 9.6.621421014 and all prior versions.

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 confidence

Stored Cross-site Scripting (XSS) vulnerability in the log view component of Secomea SiteManager allows authenticated users to inject malicious JavaScript payloads into log entries. When other users subsequently view these logs, the injected script executes in their browser context.

MitigationUpgrade to a patched version of Secomea SiteManager beyond 9.6.621421014. If immediate patching is not possible, implement output encoding/sanitization on the log view display layer to neutralize script execution.

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
Sitemanager 1129 FirmwareOperating system
Affected:< 9.6.621421014
Sitemanager 1139 FirmwareOperating system
Affected:< 9.6.621421014
Sitemanager 1149 FirmwareOperating system
Affected:< 9.6.621421014
Sitemanager 3329 FirmwareOperating system
Affected:< 9.6.621421014
Sitemanager 3339 FirmwareOperating system
Affected:< 9.6.621421014
Sitemanager 3349 FirmwareOperating system
Affected:< 9.6.621421014
Sitemanager 3529 FirmwareOperating system
Affected:< 9.6.621421014
Sitemanager 3539 FirmwareOperating system
Affected:< 9.6.621421014

CVSS 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.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Secomea SiteManager firmware version
    Access the SiteManager administrative interface and navigate to the system information or firmware status page to retrieve the currently installed firmware version number
    Affected if The installed firmware version is lower than 9.6.621421014 on any of the following models: 1129, 1139, 1149, 3329, 3339, 3349, 3529, or 3539
  2. Confirm the log view component is accessible
    Navigate to the log view or logging section within the SiteManager web interface to verify the component is present and accessible to authenticated users
    Affected if The log view component is enabled and accessible to authenticated users in the affected firmware versions
  3. Verify multi-user environment
    Check if the SiteManager has multiple user accounts configured or if remote users can authenticate and view logs
    Affected if Multiple authenticated users can access the log view component, allowing the stored XSS to affect other users viewing the same logs
  4. Inspect log entries for unsanitized content
    Review recent log entries displayed in the log view for any suspicious patterns, HTML tags, or script elements that may indicate injected payloads
    Affected if Log entries contain unescaped HTML, JavaScript tags, or event handler attributes that could execute in a browser

A user is affected if their Secomea SiteManager firmware version is less than 9.6.621421014 on the listed models and the log view component is accessible to multiple authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 9.6.621421014 or later
Fixed in 9.6.621421014
Interim mitigation

Upgrade to a patched version of Secomea SiteManager beyond 9.6.621421014. If immediate patching is not possible, implement output encoding/sanitization on the log view display layer to neutralize script execution.

Recommended fix Moderate confidence

Firmware 9.6.621421014 or later

  1. Identify the current SiteManager firmware version through the device web interface or admin console
  2. Download firmware version 9.6.621421014 or later from Secomea's official support portal (www.secomea.com)
  3. Review Secomea firmware upgrade documentation for your specific SiteManager model
  4. Upload and apply the firmware update through the SiteManager administrative interface
  5. After upgrade, verify the new firmware version is 9.6.621421014 or higher
  6. Test the log view functionality to confirm normal operation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sitemanager 1129 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-32005 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-32005 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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