CVE-2018-3781: XSS
First published: Mon Aug 13 2018(Updated: )
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.
Credit: support@hackerone.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Nextcloud Talk | <3.2.5 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-3781?
CVE-2018-3781 has a medium severity level due to the potential for stored XSS attacks requiring user interaction.
What causes CVE-2018-3781?
CVE-2018-3781 is caused by a missing sanitization of search results for an autocomplete field in NextCloud Talk versions below 3.2.5.
How do I fix CVE-2018-3781?
To fix CVE-2018-3781, upgrade NextCloud Talk to version 3.2.5 or later.
Who is affected by CVE-2018-3781?
Authenticated users of NextCloud Talk versions below 3.2.5 are affected by CVE-2018-3781.
What type of vulnerability is CVE-2018-3781?
CVE-2018-3781 is classified as a stored cross-site scripting (XSS) vulnerability.
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/weakness
- agent/last-modified-date
- agent/first-publish-date
- agent/description
- agent/event
- agent/author
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/nextcloud
- canonical/nextcloud talk