How severe is GHSA-4x7w-frcq-v4m3?

No CVSS score has been assigned to GHSA-4x7w-frcq-v4m3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4x7w-frcq-v4m3?

GHSA-4x7w-frcq-v4m3 affects the following packages: @wturyn/swagger-injector (npm). Ecosystems affected: npm.

How do I fix GHSA-4x7w-frcq-v4m3?

No patched version of @wturyn/swagger-injector has shipped for GHSA-4x7w-frcq-v4m3 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-4x7w-frcq-v4m3 in my npm dependencies?

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

How do I mitigate GHSA-4x7w-frcq-v4m3 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-4x7w-frcq-v4m3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-4x7w-frcq-v4m3 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-4x7w-frcq-v4m3 published, and has it been updated?

GHSA-4x7w-frcq-v4m3 was published on September 3, 2020 and was last updated on August 31, 2020. 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

Path Traversal in @wturyn/swagger-injectorGHSA-4x7w-frcq-v4m3

GHSA-4x7w-frcq-v4m3 is a security vulnerability in @wturyn/swagger-injector. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, 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

@wturyn/swagger-injectornpm

4downloads / week

Description

All versions of @wturyn/swagger-injector are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the configured dist folder using relative paths.

Recommendation

No fix is currently available. Consider using an alternative package until a fix is made available.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@wturyn/swagger-injector`	≥ 0.0.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @wturyn/swagger-injector, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of @wturyn/swagger-injector has shipped for GHSA-4x7w-frcq-v4m3 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

All versions of `@wturyn/swagger-injector` are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the configured `dist` folder using relative paths. ## Recommendation No fix is currently available. Consider using an alternative package until a fix is made available.

O3 Security · Impact-Aware SCA

Is GHSA-4x7w-frcq-v4m3 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works