Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

CVE-2021-29438 — @nextcloud/dialogs

MEDIUM

CVE-2021-29438 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in @nextcloud/dialogs. A fix is available for @nextcloud/dialogs — see the affected versions and patch details below.

Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in @nextcloud/dialogs

Also known asGHSA-g3fq-3v3g-mh32
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs52th percentile — riskier than 52% of all scored CVEsHighest risk
0.00%0.40%0.80%1.20%0.2%0.7%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-29438 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

10other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@nextcloud/dialogsnpm
60Kdownloads / week

Description

Impact

The Nextcloud dialogs library before 3.1.2 did insufficiently escape text input passed to a toast. If your application displays toasts with user-supplied input, this could lead to a XSS vulnerability.

Note: Nextcloud Server employs a strict Content Security Policy that mitigates the risk of these XSS vulnerabilities.

Patches

The vulnerability has been patched in version 3.1.2. If you need to display HTML in the toast, explicitly pass the options.isHTML config flag.

Workarounds

Make sure no user-supplied input flows into toasts.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@nextcloud/dialogsall versions3.1.2npm install @nextcloud/dialogs@3.1.2

Affected Products

1 product · 1 configurations
Application
nextcloud\/dialogsnextcloud\/dialogs_project
< 3.1.2
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @nextcloud/dialogs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update @nextcloud/dialogs to 3.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-29438 is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact The Nextcloud dialogs library before 3.1.2 did insufficiently escape text input passed to a toast. If your application displays toasts with user-supplied input, this could lead to a XSS vulnerability. _Note_: Nextcloud Server employs a strict Content Security Policy that mitigates the risk of these XSS vulnerabilities. ### Patches The vulnerability has been patched in version 3.1.2. If you need to display HTML in the toast, explicitly pass the `options.isHTML` config flag. ### Workarounds Make sure no user-supplied input flows into toasts.
O3 Security · Impact-Aware SCA

Is CVE-2021-29438 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2021-29438: @nextcloud/dialogs XSS — Fixed in 3.1.2