How severe is GHSA-whrh-9j4q-g7ph?

GHSA-whrh-9j4q-g7ph has a CVSS score of 6.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-whrh-9j4q-g7ph?

GHSA-whrh-9j4q-g7ph affects the following packages: polaris-website (npm). Ecosystems affected: npm.

How do I fix GHSA-whrh-9j4q-g7ph?

Update polaris-website to 1.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-whrh-9j4q-g7ph is resolved across your whole dependency graph.

How do I detect GHSA-whrh-9j4q-g7ph in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for polaris-website. 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-whrh-9j4q-g7ph 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-whrh-9j4q-g7ph?

O3 pinpoints whether GHSA-whrh-9j4q-g7ph 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-whrh-9j4q-g7ph actively exploited in the wild?

No public exploit code has been indexed for GHSA-whrh-9j4q-g7ph 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-whrh-9j4q-g7ph published, and has it been updated?

GHSA-whrh-9j4q-g7ph was published on August 5, 2020 and was last updated on September 23, 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

MEDIUM severity

GHSA-whrh-9j4q-g7ph

MEDIUMFix: polaris-rbx/Polaris-React@b64673d

GHSA-whrh-9j4q-g7ph is a medium-severity (CVSS 6.8) vulnerability in polaris-website. O3 Security confirms whether GHSA-whrh-9j4q-g7ph is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

CSRF Vulnerability in polaris-website

Published

Aug 5, 2020

Updated

Sep 23, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

📦polaris-website

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Impact

CSRF vulnerability: In some very specific circumstances, an attacker would be able to update your settings. Basically you would need to navigate to hackersite.com while logged into our panel. Then they could modify your settings. They couldn't check if it worked, nor could they read your settings.

Patches

As of v1.1.1 this has been patched by implementing the Double submit pattern using a cookie.

For more information

If you have any questions or comments about this advisory:

Open an issue in Polaris-React
Email us at [email protected]
Join our discord (preferred): https://discord.gg/QevWabU

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`polaris-website`	all versions	1.1.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for polaris-website. 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 polaris-website to 1.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-whrh-9j4q-g7ph 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-whrh-9j4q-g7ph 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-whrh-9j4q-g7ph. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact CSRF vulnerability: In some very specific circumstances, an attacker would be able to update your settings. Basically you would need to navigate to hackersite.com while logged into our panel. Then they could modify your settings. They couldn't check if it worked, nor could they read your settings. ### Patches As of v1.1.1 this has been patched by implementing the Double submit pattern using a cookie. ### For more information If you have any questions or comments about this advisory: * Open an issue in [Polaris-React](https://github.com/polaris-rbx/polaris-react) * Email us at [hi@

O3 Security · Impact-Aware SCA

Is GHSA-whrh-9j4q-g7ph in your dependencies?

O3 detects GHSA-whrh-9j4q-g7ph 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