dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-36906

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 vulnerability in iotgateway v.3.0.1 allows a remote attacker to execute arbitrary code via the Log Record Function

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 confidence

Cross-Site Scripting (XSS) vulnerability in iotgateway v3.0.1 Log Record Function allows remote attackers to inject malicious JavaScript into log entries. When other users view these logs, the injected script executes in their browsers, potentially enabling session hijacking or credential theft.

MitigationImplement input validation and output encoding on all log entry fields. Deploy Content Security Policy (CSP) headers to mitigate XSS execution. Apply vendor patch when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
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 checks

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

  1. Confirm iotgateway installation
    Locate the iotgateway application installation directory or running service on your system. Check for the presence of the iotgateway software components.
    Affected if iotgateway is installed and running
  2. Identify iotgateway version
    Check the installed version of iotgateway by inspecting the application metadata, About page, or version file. Compare against version 3.0.1.
    Affected if the installed version is 3.0.1 or falls within the affected range starting from 3.0.1
  3. Verify log record function is accessible
    Determine if the Log Record Function feature is enabled and accessible to users, either through web interface, API, or administrative console.
    Affected if the log record function is enabled and accessible to users or remote attackers
  4. Check log viewing capability
    Verify that users can view log entries through the application interface, API endpoint, or log file output.
    Affected if log viewing functionality exists and displays log content to users

You are affected if iotgateway version 3.0.1 is installed and the log record/viewing function is accessible, allowing unsanitized log entries to be displayed to 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement input validation and output encoding on all log entry fields. Deploy Content Security Policy (CSP) headers to mitigate XSS execution. Apply vendor patch when available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-36906 — 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-2026-36906 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