A missing sanitization of search results for an autocomplete field in NextCloud Talk <3.2.5 could lead to a stored XSS requiring user-inter…

published 2018-08-13 8y ago modified 2026-06-17 4mo ago also EUVD-2018-15576

cvss: 5.4; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 55%
public exploits: 0; none known

A missing sanitization of search results for an autocomplete field in NextCloud Talk <3.2.5 could lead to a stored XSS requiring user-interaction. The missing sanitization only affected user names, hence malicious search results could only be crafted by authenticated users.

Patch / fix

fixed in 1

nextcloud talk 3.2.5

Is CVE-2018-3781 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.74% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	5.4	CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD	2.0	3.5	AV:N/AC:M/Au:S/C:N/I:P/A:N

Affected products

NextCloud nextcloud/talk

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation

References

nextcloud.com /security/advisory/?id=NC-SA-2018-009
vendor-advisory
hackerone.com /reports/383117
third-party-advisory

Sources

CVE List CVE-2018-3781
NVD CVE-2018-3781

Fencer Intel 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.