How severe is GHSA-9jmq-xgjm-p8c2?

No CVSS score has been assigned to GHSA-9jmq-xgjm-p8c2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9jmq-xgjm-p8c2?

GHSA-9jmq-xgjm-p8c2 affects the following packages: @sync-in/server (npm). Ecosystems affected: npm.

How do I fix GHSA-9jmq-xgjm-p8c2?

Update @sync-in/server to 1.9.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9jmq-xgjm-p8c2 is resolved across your whole dependency graph.

How do I detect GHSA-9jmq-xgjm-p8c2 in my npm dependencies?

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

How do I mitigate GHSA-9jmq-xgjm-p8c2 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-9jmq-xgjm-p8c2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-9jmq-xgjm-p8c2 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.

What is the EPSS score for GHSA-9jmq-xgjm-p8c2?

GHSA-9jmq-xgjm-p8c2 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 25th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-9jmq-xgjm-p8c2?

GHSA-9jmq-xgjm-p8c2 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-9jmq-xgjm-p8c2 published, and has it been updated?

GHSA-9jmq-xgjm-p8c2 was published on February 20, 2026 and was last updated on February 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Sync-in Server has a stored cross-site scripting (XSS)…

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-9jmq-xgjm-p8c2.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs25th percentile — riskier than 25% of all scored CVEsHighest risk

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

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.

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

@sync-in/servernpm

2Kdownloads / week

Description

A Stored Cross-Site Scripting (XSS) vulnerability in Sync-in Server before 1.9.3 allows an authenticated attacker to execute arbitrary JavaScript in a victim's browser. By uploading a crafted SVG file containing a malicious payload, an attacker can access and exfiltrate sensitive information, including the user's session cookies.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@sync-in/server`	all versions	1.9.3`npm install @sync-in/server@1.9.3`

Affected Products

1 product · 1 configurations

Application

sync-in serversync-in

< 1.9.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @sync-in/server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @sync-in/server to 1.9.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9jmq-xgjm-p8c2 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

A Stored Cross-Site Scripting (XSS) vulnerability in Sync-in Server before 1.9.3 allows an authenticated attacker to execute arbitrary JavaScript in a victim's browser. By uploading a crafted SVG file containing a malicious payload, an attacker can access and exfiltrate sensitive information, including the user's session cookies.

O3 Security · Impact-Aware SCA

Is GHSA-9jmq-xgjm-p8c2 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

Sync-in Server has a stored cross-site scripting (XSS) vulnerabilityGHSA-9jmq-xgjm-p8c2