CVE-2021-37353
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 · uneditedNagios XI Docker Wizard before version 1.1.3 is vulnerable to SSRF due to improper sanitation in table_population.php.
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 confidenceThe Nagios XI Docker Wizard plugin before version 1.1.3 contains a Server-Side Request Forgery (SSRF) vulnerability in table_population.php due to improper input sanitization. Attackers can abuse this to make the server perform arbitrary HTTP requests to internal services or external URLs, potentially accessing internal infrastructure, bypassing firewalls, or exfiltrating data.
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< 1.1.3CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Docker Wizard plugin installationCheck the Nagios XI installation directory for the Docker Wizard component. Typical paths include /usr/local/nagiosxi/html/includes/dashlets/ or /opt/nagiosxi/html/includes/dashlets/. Look for a directory named 'docker' or 'docker_wizard'.Affected if The Docker Wizard plugin directory exists on the system
-
Identify the installed Docker Wizard versionExamine version information within the Docker Wizard directory. Check for a version.php, version.txt, or similar file. Alternatively, inspect the main PHP files for a version constant or variable definition.Affected if The version found is less than 1.1.3 or no version information is displayed (indicating an older release)
-
Verify the vulnerable table_population.php file existsSearch for table_population.php within the Docker Wizard directory structure. This file is the specific component containing the SSRF vulnerability.Affected if table_population.php exists in the Docker Wizard plugin directory
-
Check if the Docker Wizard is enabled or activeReview the Nagios XI configuration to determine if the Docker Wizard component is currently enabled. Check /usr/local/nagiosxi/etc/ or the database for plugin/component status.Affected if The Docker Wizard component shows as enabled or active in the Nagios XI configuration
The system is affected if the Docker Wizard plugin is installed with a version prior to 1.1.3 and the table_population.php file is present.
Generated from the published advisory. Verify against your own configuration.
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 data1.1.3
Upgrade the Nagios XI Docker Wizard component to version 1.1.3 or later. If immediate patching is not feasible, restrict network access to the affected endpoint and disable the Docker Wizard if not required.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37353 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-37353 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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