CVE-2021-33558 is an information exposure on devices that run the Boa 0.94.13 web server: pages such as backup.html, log.html, email.html and config.js are served without authentication. NVD scores it 7.5. The record is disputed, because those files are not part of Boa, so the fix belongs to the device vendor.
Vulnerability summary
CVSS base score
7.5
High severity
EPSS score (FIRST)
12.3%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2021-33558 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Boa web server (as named in the CVE record) | cpe:2.3:a:boa:boa:0.94.13:*:*:*:*:*:*:* | 0.94.13 (NVD); disputed: the listed files belong to the device's web interface, not to Boa |
| Device web interfaces that serve the listed pages without authentication | — | any firmware whose web root exposes backup.html, log.html, config.js or the other listed files; no vendor advisory names the products |
What does this mean for affected devices?
NVD's description says "Boa 0.94.13 allows remote attackers to obtain sensitive information via a misconfiguration involving" seven files: backup.html, preview.html, log.js in a js directory, log.html, email.html, online-users.html and config.js. It adds: "NOTE: multiple third parties report that this is a site-specific issue because those files are not part of Boa." NVD's Primary score is CVSS v3.1 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), with CVSS v2 5.0, and no CWE (NVD-CWE-noinfo). The CPE configuration lists Boa 0.94.13. The record was published on 2021-05-27 (NVD).
Is the flaw in Boa?
No. The 0.94.13 tarball on the Boa home page, Boa's last stable release, contains the server source, documentation and two example CGI scripts, and none of the seven files the record names. The reporter's proof of concept on GitHub is a list of those URLs on a target host. They are pages of a device's own web interface that Boa serves because they sit in its document root, which is why NVD's note calls it site-specific. Microsoft Threat Intelligence's November 2022 report explains why such interfaces are common: Boa, "discontinued in 2005", is built into IoT devices and chip-vendor SDKs, and their management pages are written on top of it.
How do you triage a scanner hit?
Treat the Boa version as a hint, not a finding. Unpack the firmware and list the web root: if none of the named files exist, this CVE does not apply. If they do, request them without a session on a test unit and see what comes back; a backup or configuration page served without login can expose credentials and network settings. Our embedded web server firmware guide covers locating Boa, its document root and its CGI directory in an image.
How do you fix it?
The fix is in the device's web application: put every page that returns configuration, logs, backups or user lists behind authentication, and remove debug and preview pages from production images. The authentication bypass fix guide covers enforcing a session check on every handler. Updating Boa does not change these pages, and the other disputed Boa record, CVE-2017-9833, is also in vendor code. Boa's own code flaw, CVE-2009-4496, has no upstream fix, which is one more reason to plan a move to a maintained server. The Realtek SDK web server flaw CVE-2021-35395 shows the same SDK-on-Boa pattern.
CVE-2021-33558 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.12307, the 96th percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).
Evidence
- NVD: Boa 0.94.13 sensitive information via misconfiguration involving backup.html, preview.html, log.js (js directory), log.html, email.html, online-users.html, config.js; NOTE site-specific issue because files not part of Boa; Primary CVSS v3.1 7.5 C:H, v2 5.0; NVD-CWE-noinfo; CPE boa 0.94.13; published 2021-05-27. — NVD
- boa-0.94.13.tar.gz from boa.org: top level CREDITS, ChangeLog, Gnu_License, README, boa.conf, contrib, docs, examples (cgi-test.cgi, nph-test.cgi, resolver.pl), extras, src; none of the seven listed files (checked 2026-11-18). — Boa project
- Reporter's GitHub repository: PoC lists backup.html, preview.html, log.js under js, log.html, email.html, online-users.html and config.js on a target. — GitHub (reporter)
- Microsoft Threat Intelligence (2022): Boa discontinued in 2005, implemented across IoT devices and SDKs; used to access settings, management consoles and sign-in screens. — Microsoft Security blog
- CVE-2021-33558 is not in the CISA KEV catalog, version 2026.11.17 (1,782 entries), checked 2026-11-18. — CISA KEV
- EPSS 0.12307, percentile 0.96259, dataset 2026-11-17. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Does every device with Boa 0.94.13 have CVE-2021-33558?
No. NVD notes that the listed files are not part of Boa, and the Boa 0.94.13 source tarball contains none of them. Only a device whose web interface serves those pages without authentication is affected (per NVD and the Boa source).
Which files does CVE-2021-33558 refer to?
backup.html, preview.html, log.js in a js directory, log.html, email.html, online-users.html and config.js. They belong to a device's web interface, and the record says they expose sensitive information to remote attackers (per NVD and the reporter's proof of concept).
How do I fix CVE-2021-33558 if my product uses Boa?
Require authentication on every page that returns configuration, logs, backups or user data, and remove debug and preview pages from production firmware. Updating Boa does not help: its last stable release is 0.94.13, the home page was last updated in February 2005, and the files are not Boa's (per NVD and the Boa home page).
Is CVE-2021-33558 in the CISA KEV catalog?
No, not as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.12307, the 96th percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?