How severe is GHSA-gxp8-m5rq-3m38?

No CVSS score has been assigned to GHSA-gxp8-m5rq-3m38 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gxp8-m5rq-3m38?

GHSA-gxp8-m5rq-3m38 affects the following packages: qwc2 (npm). Ecosystems affected: npm.

How do I fix GHSA-gxp8-m5rq-3m38?

Update qwc2 to 2025.08.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gxp8-m5rq-3m38 is resolved across your whole dependency graph.

How do I detect GHSA-gxp8-m5rq-3m38 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for qwc2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-gxp8-m5rq-3m38 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-gxp8-m5rq-3m38?

O3 pinpoints whether GHSA-gxp8-m5rq-3m38 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-gxp8-m5rq-3m38 actively exploited in the wild?

No public exploit code has been indexed for GHSA-gxp8-m5rq-3m38 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 type of vulnerability is GHSA-gxp8-m5rq-3m38?

GHSA-gxp8-m5rq-3m38 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-gxp8-m5rq-3m38 published, and has it been updated?

GHSA-gxp8-m5rq-3m38 was published on October 13, 2025 and was last updated on October 13, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-gxp8-m5rq-3m38

GHSA-gxp8-m5rq-3m38 is a Cross-site Scripting (XSS) vulnerability in qwc2. O3 Security confirms whether GHSA-gxp8-m5rq-3m38 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

QGIS QWC2 Cross-Site Scripting vulnerability

Also known asCVE-2025-11183

Published

Oct 13, 2025

Updated

Oct 13, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

qwc2npm

458downloads / week

Description

Cross-Site Scripting vulnerability in attribute table in QGIS QWC2 < 2025.08.14 allows an authorized attacker to plant arbitrary JavaScript code in the page.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`qwc2`	all versions	2025.08.14

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for qwc2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update qwc2 to 2025.08.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gxp8-m5rq-3m38 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-gxp8-m5rq-3m38 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-gxp8-m5rq-3m38. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Cross-Site Scripting vulnerability in attribute table in QGIS QWC2 < 2025.08.14 allows an authorized attacker to plant arbitrary JavaScript code in the page.

O3 Security · Impact-Aware SCA

Is GHSA-gxp8-m5rq-3m38 in your dependencies?

O3 detects GHSA-gxp8-m5rq-3m38 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works