Skip to content
Fencer Vulns
medium 5.4

CVE-2023-23942 json

Self reflected HTML injection in Desktop client

published 2023-02-06 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-28008

cvss
5.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

Summary

The Nextcloud Desktop Client is a tool to synchronize files from a Nextcloud Server with your computer. Versions prior to 3.6.3 are missing sanitisation on qml labels which are used for basic HTML elements such as `strong`, `em` and `head` lines in the UI of the desktop client. The lack of sanitisation may allow for javascript injection. It is recommended that the Nextcloud Desktop Client is upgraded to 3.6.3. There are no known workarounds for this issue.

Patch / fix

  • nextcloud desktop 3.6.3
  • nextcloud-desktop Debian 14, Debian 13, Debian 12 3.6.4-1

debian advisories DEBIAN-CVE-2023-23942

  • nextcloud-desktop Package Hub 15 SP5, openSUSE Leap 15.5 3.8.0-bp155.2.3.1
  • nextcloud-desktop Package Hub 15 SP4, openSUSE Leap 15.4 3.8.0-bp154.2.3.1

opensuse advisories openSUSE-SU-2023:0171-1openSUSE-SU-2023:0090-1

  • nextcloud-client Alpine 3.24, Alpine 3.23, Alpine 3.22 +4 more 3.6.6-r0

alpine advisories ALPINE-CVE-2023-23942

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
19 mo ago

Exploit prediction

0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected products

  • nextcloud security-advisories

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.