dbcve.org
TalkApplication · Nextcloud

CVE-2018-3781

MEDIUM · 5.4 CVSS v3.0 Published 2018-08-13
Fix available
A fix is available. Upgrade to 3.2.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
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.

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 confidence

A stored XSS vulnerability in NextCloud Talk versions before 3.2.5 exists due to missing sanitization of user names in the autocomplete search results. Authenticated users can craft malicious usernames containing JavaScript code that executes in other users' browsers when they interact with the autocomplete field, requiring user-interaction to trigger.

MitigationUpgrade NextCloud Talk to version 3.2.5 or later which includes proper sanitization of autocomplete search results.

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
TalkApplication
Affected:< 3.2.5

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.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify NextCloud Talk is installed
    Check the apps list in NextCloud admin panel or query the occ command: 'occ app:list' to see if 'spreed' or 'talk' app is enabled
    Affected if NextCloud Talk app is not installed or not applicable if not using Talk
  2. Determine NextCloud Talk version
    Run 'occ app:list' or check the Talk app details in the admin panel under Apps > Productivity > Talk to find the installed version number
    Affected if Unable to determine the installed version
  3. Compare version against affected range
    Compare your installed NextCloud Talk version to 3.2.5 - any version lower than 3.2.5 is affected
    Affected if Installed version is less than 3.2.5 (e.g., 3.2.4, 3.2.0, 3.1.x, etc.)
  4. Confirm autocomplete feature is accessible
    Test that the Talk autocomplete search is functional - type a character in the To: field or participant search in a chat conversation to trigger autocomplete
    Affected if Autocomplete feature is accessible to authenticated users (standard Talk functionality)

You are affected if NextCloud Talk is installed with a version lower than 3.2.5 and users can access the autocomplete search feature in conversations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 3.2.5 or later
Fixed in 3.2.5
Interim mitigation

Upgrade NextCloud Talk to version 3.2.5 or later which includes proper sanitization of autocomplete search results.

Fix this in Talk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-3781 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-3781 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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