CVE-2022-47187
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 · uneditedThere is a file upload XSS vulnerability in Generex CS141 below 2.06 version. The web application allows file uploading, making it possible to upload a file with HTML content. When HTML files are allowed, XSS payload can be injected into the uploaded file.
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 confidenceThere is a stored Cross-Site Scripting (XSS) vulnerability in Generex CS141 web application versions below 2.06. The application allows file uploads and permits HTML files to be uploaded without proper sanitization or validation. An attacker can upload a malicious HTML file containing XSS payloads that will execute when other users view or access the uploaded file.
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< 2.06CVSS 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.
-
Determine the installed firmware versionAccess the Generex CS141 web interface and navigate to System > Status, System > Information, or the About page to locate the firmware version. If direct device access is available, check the version displayed in the admin panel or device status screen.Affected if The installed firmware version is below 2.06
-
Verify if file upload functionality existsLog into the CS141 web application and explore the navigation menus for file upload capabilities. Look for sections such as File Management, Backup/Restore, Configuration Upload, Dashboard widgets, or any feature that accepts file uploads.Affected if A file upload feature is present and accessible in the web application
-
Test if HTML file uploads are permittedThrough the identified upload feature, attempt to upload a test file with an .html extension. Submit the file through the upload form and confirm whether the server accepts and stores the HTML file without rejecting it based on file type.Affected if HTML files can be uploaded and stored on the server without being blocked or sanitized
The environment is affected if the Generex CS141 firmware version is below 2.06 and the file upload feature allows HTML files to be uploaded and stored.
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.
dbcve · scoped2.06
Upgrade to Generex CS141 version 2.06 or later which contains the fix. Additionally, implement strict file type validation to disallow HTML file uploads, or sanitize uploaded file content to strip potentially malicious scripts before storage.
Cs141 Firmware version 2.06
- Identify the current Generex CS141 Firmware version in use
- Download firmware version 2.06 or later from the official Generex source (www.generex.de)
- Review firmware upgrade documentation provided by Generex
- Perform a backup of the current configuration
- Upload and install the firmware version 2.06 following the vendor's recommended procedure
- Verify the installation was successful and the device is operational
- Confirm that HTML file uploads are now properly sanitized or blocked
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47187 — 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-2022-47187 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