CVE-2021-33848
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 · uneditedFresenius Kabi Vigilant Software Suite (Mastermed Dashboard) version 2.0.1.3 is vulnerable to reflected cross-site scripting attacks. An attacker could inject JavaScript in a GET parameter of HTTP requests and perform unauthorized actions such as stealing internal information and performing actions in context of an authenticated user.
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 confidenceFresenius Kabi Vigilant Software Suite Mastermed Dashboard 2.0.1.3 contains a reflected cross-site scripting (XSS) vulnerability where malicious JavaScript can be injected through GET parameters in HTTP requests. This allows attackers to execute arbitrary scripts in the context of an authenticated user's session, enabling data theft and unauthorized actions.
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<= d25<= 3.3.0= 1.0= 1.0= 1.0< 3.0= 3.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Fresenius Kabi productLocate the installed Fresenius Kabi software on the system (e.g., Vigilant Mastermed, Vigilant Centerium, Vigilant Insight, Agilia Connect, Agilia Partner Maintenance, or Link+ Agilia). Check installed programs or services for the product name.Affected if Any of the listed affected products (Vigilant Mastermed 1.0, Vigilant Centerium 1.0, Vigilant Insight 1.0, Agilia Connect Firmware <= d25, Agilia Partner Maintenance Software <= 3.3.0, or Link+ Agilia Firmware < 3.0 or = 3.0) is installed.
-
Verify product versionCheck the installed version of the Fresenius Kabi product against the affected version ranges provided. Compare your installed version number to: Vigilant Mastermed = 1.0, Vigilant Centerium = 1.0, Vigilant Insight = 1.0, Agilia Connect Firmware <= d25, Agilia Partner Maintenance Software <= 3.3.0, Link+ Agilia Firmware < 3.0 or = 3.0.Affected if The installed version matches or falls within any of the affected version ranges.
-
Confirm web interface accessibilityDetermine if the application's web interface is accessible by attempting to reach the application URL or checking if the web service is listening on its expected port (consult product documentation for default port).Affected if The web interface is exposed and reachable.
-
Check for unauthenticated parameter accessSend a GET request to the application with a test parameter containing a harmless string (e.g., ?test=123) and observe if the application reflects the parameter value in the response without proper encoding.Affected if The application reflects user-supplied GET parameter values directly in HTML output without sanitization.
You are affected if you have any of the listed Fresenius Kabi products (Mastermed, Centerium, Insight, Agilia Connect, Agilia Partner Maintenance, or Link+ Agilia) installed and running, and the version matches the affected ranges with the web interface accessible.
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 data3.0
Implement proper input validation and output encoding for all user-supplied GET parameters, and deploy Content Security Policy (CSP) headers to mitigate XSS execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33848 — 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-33848 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