Skip to content

← Public intelligence

npm package

status-board

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.1npmAmendedPublished

    Cross-Site Scripting in status-board

    CVE-2019-15478 · GHSA-6m4r-cgm3-6q7q

    Affected
    • npm status-board < 1.1.82
    Fixed in
    1.1.82· Vendor fix available
    Issue
    All versions of status-board are vulnerable to Cross-Site Scripting. The renderJsDashboard() function concatenates the safeDashboard variable to the HTTP response message with insufficient sanitization. If this variable is controlled by user input it may allow attackers to execute arbitrary JavaScript in a victim's browser. Recommendation No fix is currently available. Consider using an alternative package until a fix is made available.

    Recommended action: Upgrade to 1.1.82 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. Medium, CVSS 6.1npmAmendedPublished

    Status Board vulnerable to Cross-Site Scripting before v1.1.82

    CVE-2019-15479 · GHSA-8864-rhmw-5m6f

    Affected
    • npm status-board < 1.1.82
    Fixed in
    1.1.82· Vendor fix available
    Issue
    Versions of status-board prior to 1.1.82 are vulnerable to Cross-Site Scripting. The renderDashboard() function concatenates the safeDashboard variable to the printed error message with insufficient sanitization. If this variable is controlled by user input it allows attackers to execute arbitrary JavaScript in a victim's browser. Recommendation Upgrade to version 1.1.82 to receive a patch.

    Recommended action: Upgrade to 1.1.82 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →