How severe is GHSA-2r2v-9pf8-6342?

No CVSS score has been assigned to GHSA-2r2v-9pf8-6342 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2r2v-9pf8-6342?

GHSA-2r2v-9pf8-6342 affects the following packages: github.com/h44z/wg-portal (Go). Ecosystems affected: Go.

How do I fix GHSA-2r2v-9pf8-6342?

Update github.com/h44z/wg-portal to 2.0.0-alpha.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2r2v-9pf8-6342 is resolved across your whole dependency graph.

How do I detect GHSA-2r2v-9pf8-6342 in my Go dependencies?

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

How do I mitigate GHSA-2r2v-9pf8-6342 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-2r2v-9pf8-6342?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2r2v-9pf8-6342 can be triaged on real exposure rather than presence alone.

Is GHSA-2r2v-9pf8-6342 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2r2v-9pf8-6342 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-2r2v-9pf8-6342 published, and has it been updated?

GHSA-2r2v-9pf8-6342 was published on January 7, 2025 and was last updated on January 8, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-2r2v-9pf8-6342 — wg-portal

Fix: h44z/wg-portal@62dbdfe

GHSA-2r2v-9pf8-6342 is a security vulnerability in github.com/h44z/wg-portal. A fix is available for github.com/h44z/wg-portal — see the affected versions and patch details below.

WireGuard Portal v2 Vulnerable to OAuth Insecure Redirect URI / Account Takeover

Also known asGO-2025-3371

Published

Jan 7, 2025

Updated

Jan 8, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jan 8, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/h44z/wg-portal

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

Description

Impact

Users of WireGuard Portal v2 who have OAuth (or OIDC) authentication backends enabled can be affected by an Account Takeover vulnerability if they visit a malicious website.

Patches

The problem was fixed in the latest alpha release, v2.0.0-alpha.3. The docker images for the tag 'latest' built from the master branch also include the fix.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/h44z/wg-portal`	≥ 2.0.0-alpha.1&&< 2.0.0-alpha.3	2.0.0-alpha.3`go get github.com/h44z/wg-portal@v2.0.0-alpha.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/h44z/wg-portal, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/h44z/wg-portal to 2.0.0-alpha.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2r2v-9pf8-6342 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2r2v-9pf8-6342 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-2r2v-9pf8-6342. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Users of WireGuard Portal v2 who have OAuth (or OIDC) authentication backends enabled can be affected by an Account Takeover vulnerability if they visit a malicious website. ### Patches The problem was fixed in the latest alpha release, v2.0.0-alpha.3. The [docker images](https://hub.docker.com/r/wgportal/wg-portal) for the tag 'latest' built from the master branch also include the fix.

O3 Security · Impact-Aware SCA

Is GHSA-2r2v-9pf8-6342 in your dependencies?

O3 Security finds GHSA-2r2v-9pf8-6342 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works