VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

iobroker.web: vulnerability history, versions and safety

iobroker.web is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 2 releases, first recorded in Dec 2019. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all iobroker.web vulnerabilities

Vulert verdict on iobroker.web 9.1.16 i

Updated on 23 Oct 2026

Good news: 9.1.16, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 71/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

What to do: Stay on 9.1.16 or newer. This can change: a vulnerability disclosed tomorrow can affect 9.1.16 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 9.1.16 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 02 Dec 2019 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 3 packages i
  • Stars 49 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for iobroker.web, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
9.1.16 21 Oct 2026 none MIT — Details →
9.1.15 14 Oct 2026 none MIT — Details →
9.1.14 11 Oct 2026 none MIT — Details →
9.1.13 11 Oct 2026 none MIT — Details →
9.1.12 04 Oct 2026 none MIT — Details →
9.1.11 02 Oct 2026 none MIT — Details →
9.1.10 02 Oct 2026 none MIT — Details →
9.1.9 28 Sep 2026 none MIT — Details →
9.1.8 24 Sep 2026 none MIT — Details →
9.1.7 21 Sep 2026 none MIT — Details →
9.1.4 31 Aug 2026 none MIT — Details →
9.1.3 28 Aug 2026 none MIT — Details →
9.1.2 27 Aug 2026 none MIT — Details →
9.1.1 26 Aug 2026 none MIT — Details →
9.1.0 04 Aug 2026 none MIT — Details →
9.0.0 21 Jun 2026 none MIT — Details →
8.3.0 12 Jun 2026 none MIT — Details →
8.1.0 13 Apr 2026 none MIT — Details →
8.0.0 17 Feb 2026 none MIT — Details →
7.0.9 28 Mar 2025 none MIT — Details →
7.0.8 18 Mar 2025 none MIT — Details →
7.0.7 15 Mar 2025 none MIT — Details →
7.0.6 09 Mar 2025 none MIT — Details →
7.0.5 09 Mar 2025 none MIT — Details →
7.0.4 04 Mar 2025 none MIT — Details →
7.0.3 03 Mar 2025 none MIT — Details →
6.3.1 23 Sep 2024 none MIT — Details →
6.3.0 27 Jun 2024 none MIT — Details →
6.2.6 25 May 2024 none MIT — Details →
6.2.5 22 Feb 2024 none MIT — Details →
6.2.4 17 Feb 2024 none MIT — Details →
6.2.3 18 Dec 2023 none MIT — Details →
6.2.2 14 Dec 2023 none MIT — Details →
6.2.1 04 Dec 2023 none MIT — Details →
6.1.10 16 Oct 2023 none MIT — Details →
6.1.7 16 Oct 2023 none MIT — Details →
6.1.6 13 Oct 2023 none MIT — Details →
6.1.5 11 Oct 2023 none MIT — Details →
6.1.4 08 Oct 2023 none MIT — Details →
6.1.3 28 Sep 2023 none MIT — Details →
6.1.2 14 Sep 2023 none MIT — Details →
6.1.1 05 Sep 2023 none MIT — Details →
6.1.0 01 Aug 2023 none MIT — Details →
6.0.3 27 Jul 2023 none MIT — Details →
5.5.3 17 Mar 2023 none MIT — Details →
5.5.2 03 Mar 2023 none MIT — Details →
5.5.1 25 Feb 2023 none MIT — Details →
5.5.0 15 Feb 2023 none MIT — Details →
5.4.3 29 Jan 2023 none MIT — Details →
5.4.1 23 Dec 2022 none MIT — Details →
5.4.0 22 Dec 2022 none MIT — Details →
5.3.1 27 Nov 2022 none MIT — Details →
5.3.0 27 Nov 2022 none MIT — Details →
5.2.12 18 Nov 2022 none MIT — Details →
5.2.10 10 Oct 2022 none MIT — Details →
5.2.9 10 Oct 2022 none MIT — Details →
5.2.8 09 Oct 2022 none MIT — Details →
5.2.5 24 Aug 2022 none MIT — Details →
5.2.4 08 Jul 2022 none MIT — Details →
5.2.3 20 Jun 2022 none MIT — Details →
5.2.2 09 Jun 2022 none MIT — Details →
5.2.1 09 Jun 2022 none MIT — Details →
5.2.0 22 May 2022 none MIT — Details →
5.1.2 20 May 2022 none MIT — Details →
5.1.1 20 May 2022 none MIT — Details →
5.1.0 20 May 2022 none MIT — Details →
5.0.3 20 May 2022 none MIT — Details →
5.0.1 20 May 2022 none MIT — Details →
5.0.0 19 May 2022 none MIT — Details →
4.3.0 15 Apr 2022 none MIT — Details →
4.2.3 28 Mar 2022 none MIT — Details →
4.2.1 18 Mar 2022 none MIT — Details →
4.2.0 21 Feb 2022 none MIT — Details →
4.1.6 19 Feb 2022 none MIT — Details →
4.1.5 16 Feb 2022 none MIT — Details →
4.1.4 14 Feb 2022 none MIT — Details →
4.1.3 13 Feb 2022 none MIT — Details →
4.1.1 01 Feb 2022 none MIT — Details →
4.1.0 31 Jan 2022 none MIT — Details →
4.0.1 30 Jan 2022 none MIT — Details →
4.0.0 29 Jan 2022 none MIT — Details →
3.4.16 15 Nov 2021 none MIT — Details →
3.4.15 15 Nov 2021 none MIT — Details →
3.4.14 15 Nov 2021 none MIT — Details →
3.4.13 25 Oct 2021 none MIT — Details →
3.4.12 23 Oct 2021 none MIT — Details →
3.4.11 22 Oct 2021 none MIT — Details →
3.4.10 22 Oct 2021 none MIT — Details →
3.4.9 11 Aug 2021 none MIT — Details →
3.4.8 10 Aug 2021 none MIT — Details →
3.4.7 31 Jul 2021 none MIT — Details →
3.4.6 31 Jul 2021 none MIT — Details →
3.4.5 20 Jul 2021 none MIT — Details →
3.4.4 03 Jul 2021 none MIT — Details →
3.4.3 01 Jul 2021 none MIT — Details →
3.4.2 01 Jul 2021 none MIT — Details →
3.4.1 30 Apr 2021 none MIT — Details →
3.4.0 12 Apr 2021 none MIT — Details →
3.3.0 01 Feb 2021 none MIT — Details →
3.2.3 12 Jan 2021 none MIT — Details →
3.2.0 08 Jan 2021 none — — Details →
3.1.1 08 Jan 2021 none — — Details →
3.1.0 26 Nov 2020 none — — Details →
3.0.14 30 Oct 2020 none — — Details →
3.0.13 06 Sep 2020 none — — Details →
3.0.12 22 Aug 2020 none — — Details →
3.0.11 21 Aug 2020 none — — Details →
3.0.10 27 Jul 2020 none — — Details →
3.0.9 10 Jun 2020 none — — Details →
3.0.8 04 May 2020 none — — Details →
3.0.7 30 Apr 2020 none — — Details →
3.0.6 30 Apr 2020 none — — Details →
3.0.5 23 Apr 2020 none — — Details →
3.0.4 16 Apr 2020 none — — Details →
3.0.2 12 Mar 2020 none — — Details →
3.0.1 23 Feb 2020 none — — Details →
3.0.0 06 Feb 2020 none — — Details →
2.4.10 09 Nov 2019 none — — Details →
2.4.9 04 Nov 2019 M1 — Yes Details →
2.4.8 22 Oct 2019 M1 — Yes Details →

The newest 120 of 188 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for iobroker.web

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-10771: Cross-Site Scripting in iobroker.web 6.1 medium 2.4.10 02 Dec 2019

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About iobroker.web

Is iobroker.web safe to use?

Vulert records 1 vulnerabilities for iobroker.web in npm: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is iobroker.web's Vulert package health score?

Vulert scores iobroker.web 71/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of iobroker.web affected?

No. 9.1.16, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does iobroker.web have?

1 vulnerability is recorded for iobroker.web in the npm ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new iobroker.web vulnerabilities disclosed?

0 vulnerabilities were recorded for iobroker.web in the last 12 months, and the oldest entry in this database dates to 02 Dec 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of iobroker.web are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor iobroker.web for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the iobroker.web version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.