WireGuard Portal is Vulnerable to Privilege Escalation via User Self-Update to Admin Level

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-27899: 0.35% estimated exploitation activity in the next 30 days; percentile 28.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Privilege Escalation to Admin via User Self-Update in wg-portal Summary Any authenticated non-admin user can become a full administrator by sending a single PUT request to their own user profile endpoint with "IsAdmin": true in the JSON body. After logging out and back in, the session picks up admin privileges from the database. Tested against wg-portal v2.1.2 (Docker image wgportal/wg-portal:v2). Root Cause When a user updates their own profile, the server parses the full JSON body into the user model, including the IsAdmin boolean field. A function responsible for preserving calculated or protected attributes pins certain fields to their database values (such as base model data, linked peer count, and authentication data), but it does not do this for IsAdmin. As a result, whatever value the client sends for IsAdmin is written directly to the database. Impact After the exploit, the attacker has full admin access to the WireGuard VPN management portal. They can: - Read and modify…

Published by the source

26 Feb 2026, 22:22 UTC

Last modified by the source

26 Feb 2026, 22:22 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5rmx-256w-8mj9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-27899

Advisory: WireGuard Portal is Vulnerable to Privilege Escalation via User Self-Update to Admin Level
IDs: CVE-2026-27899, GHSA-5rmx-256w-8mj9
Record: https://patchnext.com/advisories/cve-2026-27899 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/h44z/wg-portal 2.1.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/h44z/wg-portal: affected <= 2.1.2; fixed in 2.1.3

## Suggested inspection (read-only)
- Go github.com/h44z/wg-portal: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/h44z/wg-portal.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5rmx-256w-8mj9 (GitHub-reviewed advisory GHSA-5rmx-256w-8mj9 lists affected ranges: Go github.com/h44z/wg-portal >=0 <=2.1.2)

Commands are suggestions: review each one before running it.