CVE-2022-45179
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 issue was discovered in LIVEBOX Collaboration vDesk through v031. A basic XSS vulnerability exists under the /api/v1/vdeskintegration/todo/createorupdate endpoint via the title parameter and /dashboard/reminders. A remote user (authenticated to the product) can store arbitrary HTML code in the reminder section title in order to corrupt the web page (for example, by creating phishing sections to exfiltrate victims' credentials).
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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in LIVEBOX Collaboration vDesk. The /api/v1/vdeskintegration/todo/createorupdate endpoint accepts a title parameter that is not properly sanitized, allowing authenticated users to store arbitrary HTML/JavaScript code. This malicious payload is then rendered in the /dashboard/reminders section, enabling attackers to create phishing pages to exfiltrate user credentials.
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<= 031CVSS 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 Liveboxcloud Vdesk versionCheck the installed version of Liveboxcloud Vdesk in the application UI, About section, or by querying the API for version information. Compare against the affected range: version 031 and below.Affected if Installed version is 031 or lower (any version <= 031)
-
Verify authenticated access to the applicationConfirm you have valid authentication credentials for the Liveboxcloud Vdesk portal. The vulnerability requires an authenticated user to submit the malicious payload.Affected if User has valid login credentials for the vDesk application
-
Confirm the createorupdate endpoint is reachableCheck if the API endpoint /api/v1/vdeskintegration/todo/createorupdate exists and responds to requests. This can be verified by inspecting network traffic or attempting a controlled API call with valid auth.Affected if The /api/v1/vdeskintegration/todo/createorupdate endpoint is accessible and accepts requests with a title parameter
-
Check if reminders dashboard is in useVerify that the /dashboard/reminders section exists and displays data submitted through the createorupdate endpoint. Inspect whether user-supplied title content is rendered in this area.Affected if The /dashboard/reminders page renders content from the title parameter without sanitization
A user is affected if they are running Liveboxcloud Vdesk version 031 or lower AND have authenticated access to the application where the vulnerable endpoint and reminders dashboard are 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 dataImplement input validation and output encoding/sanitization on the title parameter in the createorupdate endpoint and all similar user-supplied content rendered in the dashboard. Use context-appropriate encoding when rendering reminder data.
- 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-2022-45179 — 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-45179 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