How severe is GHSA-r3xc-47qg-h929?

No CVSS score has been assigned to GHSA-r3xc-47qg-h929 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r3xc-47qg-h929?

GHSA-r3xc-47qg-h929 affects the following packages: @ionic/core (npm), @ionic/core (npm), @ionic/core (npm), @ionic/core (npm). Ecosystems affected: npm.

How do I fix GHSA-r3xc-47qg-h929?

Update @ionic/core to 4.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r3xc-47qg-h929 is resolved across your whole dependency graph.

How do I detect GHSA-r3xc-47qg-h929 in my npm dependencies?

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

How do I mitigate GHSA-r3xc-47qg-h929 if there is no patch (or I can't update yet)?

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.

Is GHSA-r3xc-47qg-h929 actively exploited in the wild?

No public exploit code has been indexed for GHSA-r3xc-47qg-h929 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-r3xc-47qg-h929 published, and has it been updated?

GHSA-r3xc-47qg-h929 was published on September 3, 2020 and was last updated on September 28, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Cross-Site Scripting in @ionic/coreGHSA-r3xc-47qg-h929

GHSA-r3xc-47qg-h929 is a security vulnerability in @ionic/core. A fix is available for @ionic/core — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Sep 28, 2021

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Sep 28, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

4 pkgs 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.

288other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@ionic/corenpm

510Kdownloads / week

Description

Versions of @ionic/core prior to 4.0.3, 4.1.3, 4.2.1 or 4.3.1 are vulnerable to Cross-Site Scripting (XSS). The package uses the unsafe innerHTML function without sanitizing input, which may allow attackers to execute arbitrary JavaScript on the victim's browser. This issue affects the components:

<ion-alert>.message
<ion-searchbar>.placeholder
<ion-infinite-scroll-content>.loadingText
<ion-refresher-content>.pullingText
<ion-refresher-content>.refershingText

Recommendation

If you are using @ionic/core 4.0.x, upgrade to 4.0.3 or later.
If you are using @ionic/core 4.1.x, upgrade to 4.1.3 or later.
If you are using @ionic/core 4.2.x, upgrade to 4.2.1 or later.
If you are using @ionic/core 4.3.x, upgrade to 4.3.1 or later.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@ionic/core`	all versions	4.0.3`npm install @ionic/core@4.0.3`
📦npm	`@ionic/core`	≥ 4.1.0&&< 4.1.3	4.1.3`npm install @ionic/core@4.1.3`
📦npm	`@ionic/core`	≥ 4.2.0&&< 4.2.1	4.2.1`npm install @ionic/core@4.2.1`
📦npm	`@ionic/core`	≥ 4.3.0&&< 4.3.1	4.3.1`npm install @ionic/core@4.3.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @ionic/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @ionic/core to 4.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r3xc-47qg-h929 is resolved across your whole dependency graph.
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

Versions of `@ionic/core` prior to 4.0.3, 4.1.3, 4.2.1 or 4.3.1 are vulnerable to Cross-Site Scripting (XSS). The package uses the unsafe `innerHTML` function without sanitizing input, which may allow attackers to execute arbitrary JavaScript on the victim's browser. This issue affects the components: - `<ion-alert>.message` - `<ion-searchbar>.placeholder` - `<ion-infinite-scroll-content>.loadingText` - `<ion-refresher-content>.pullingText` - `<ion-refresher-content>.refershingText` ## Recommendation - If you are using @ionic/core 4.0.x, upgrade to 4.0.3 or later. - If you are using @ionic

O3 Security · Impact-Aware SCA

Is GHSA-r3xc-47qg-h929 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works