CVE-2026-36162
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 · uneditedAn authenticated stored cross-site scripting (XSS) vulnerability in the Upload File Shares API of LiquidFiles v4.2.7 allows attackers to execute arbitrary Javascript or HTML via injecting a crafted payload into the Name parameter.
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 confidenceAuthenticated stored XSS vulnerability in LiquidFiles v4.2.7 allows authenticated attackers to inject malicious JavaScript or HTML into the Name parameter of the Upload File Shares API, which is then executed when the payload is rendered in the application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 LiquidFiles installation and versionLocate the LiquidFiles application and determine its installed version by checking the web interface (typically in Help > About or similar), or querying the API endpoint for version informationAffected if The installed version is 4.2.7 exactly or falls within the 4.2.x branch prior to remediation
-
Confirm authentication access to the APIVerify that a valid user account exists with permissions to access the Upload File Shares API endpoint. Check user roles and API key access if applicableAffected if An authenticated user account with API access exists in the system
-
Locate the Upload File Shares API endpointIdentify if the file shares functionality is accessible via API - typically at an endpoint like /api/file_shares or similar under the LiquidFiles web root. Check API documentation or network traffic for usageAffected if The Upload File Shares API endpoint is enabled and accessible to authenticated users
-
Inspect stored file shares for XSS payloadsQuery the database or use the API to list all file shares and examine the 'Name' field for any suspicious patterns such as <script>, javascript:, onload, onerror, or other HTML/JS tagsAffected if Any file share record contains HTML or JavaScript code in the Name parameter that was not intentionally encoded
-
Check application logs for XSS injection attemptsReview LiquidFiles server logs for POST requests to the file shares API containing XSS patterns in the Name parameter fieldAffected if Logs show requests with XSS payloads in the Name parameter from authenticated users
You are affected if running LiquidFiles version 4.2.7 and have authenticated users who can access the Upload File Shares API, as the stored XSS will execute when the Name field is rendered.
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 dataImplement strict input validation and output encoding on the Name parameter in the Upload File Shares API to prevent XSS execution.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36162 — 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-2026-36162 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