Skip to main content
VulnerabilityPublished

CVE-2026-27899: h44z wg-portal · Improper Privilege Management

Affects h44z wg-portalSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 2.1.3 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.1.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade wg-portal and h44z/wg-portal to 2.1.3.

Affected software

ProductAffectedFixed in
h44zwg-portalAffected
  • <2.1.3
Fixed in
  • 2.1.3
GitHubh44z/wg-portalpkg:github/h44z/wg-portalOther threatsAffected
  • <2.1.3
Fixed in
  • 2.1.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, organizations should immediately upgrade wg-portal to version 2.1.3 or later, where the privilege escalation flaw has been fixed. For deployments using Docker images, ensure that the 'latest' tag or images built from the master branch are used, as they include the patch. Additionally, implement strict access controls to limit the number of users with authenticated access to the portal, especially non-admin users. Monitor access logs for unusual PUT requests to user profile endpoints that attempt to modify privilege-related fields. Employ network segmentation to restrict access to the wg-portal interface to trusted management networks only. Consider implementing multi-factor authentication (MFA) for all users to reduce the risk of compromised credentials being used to exploit this vulnerability. Regularly audit user privileges and database records to detect unauthorized privilege escalations. Finally, maintain an incident response plan to quickly address any suspected compromise stemming from this vulnerability.

Description

WireGuard Portal (or wg-portal) is a web-based configuration portal for WireGuard server management. Prior to version 2.1.3, 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. 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. After the exploit, the attacker has full admin access to the WireGuard VPN management portal. The problem was fixed in v2.1.3. The docker images for the tag 'latest' built from the master branch also include the fix.

References

Community reviews

Loading reviews…