Skip to main content
Mallory
← Back to News
internet-facing-service-vulnerabilityprivilege-escalation-methodwidely-deployed-product-advisoryinitial-access-method

UpSnap flaws allowed superuser takeover and remote code execution

Vulnerability Disclosure · 3 sources · Updated 3mo ago · First seen Aug 13, 2026

UpSnap flaws allowed superuser takeover and remote code execution

UpSnap disclosed and patched two high-severity vulnerabilities in version 5.4.0 affecting the wake-on-LAN web application. One flaw, tracked as CVE-2026-49819, affected fresh installations from versions 4.4.1 through 5.3.5 and allowed an unauthenticated network-adjacent attacker to complete the initial setup flow first, claim the first superuser account, and obtain a long-lived JWT. The issue could then be chained into root-level remote code execution through the application's wake functionality, yielding a CVSS 9.8 rating.

A second flaw, CVE-2026-49481, was an authenticated OS command injection bug in device management that let a low-privileged user inject shell metacharacters into IP or MAC fields used by wake_cmd and shutdown_cmd, leading to command execution via /bin/sh -c on Linux or cmd /C on Windows. UpSnap said the initial setup issue does not affect instances that were already fully initialized, while the command injection risk primarily impacts deployments where untrusted users can create or edit devices. The project mitigated the bugs by moving first superuser creation to a one-time PocketBase link shown only in server console logs, validating IP and MAC values in the backend, adding PocketBase regex constraints, and enforcing browser-side input patterns.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

3 events · May 26, 2026 – Aug 13, 2026
  1. Aug 13, 20263mo ago

    CVE-2026-49819 published for initial-superuser takeover chain

    A CVE entry was published for a critical UpSnap vulnerability chain affecting versions 4.4.1 through 5.3.5, in which an unauthenticated attacker on a fresh install could register the initial superuser account and potentially chain this to root remote code execution. The entry links the issue to GitHub advisory GHSA-w4jr-728f-5jhq and recommends upgrading to version 5.4.0 or later and removing unauthorized superuser accounts.

    CVE-2026-49819 - UpSnap - Unauthenticated Initial-Superuser Takeover Chains to Root RCE via wake_cmd
  2. Aug 12, 20263mo ago

    CVE-2026-49481 record received for UpSnap command injection flaw

    The CVE record for UpSnap's device IP and MAC command injection vulnerability was received by security-advisories@github.com. The issue affects versions prior to 5.4.0 and allows a low-privileged user who can create or edit devices to achieve authenticated remote code execution.

    CVE-2026-49481 - UpSnap vulnerable to Remote Code Execution via IP Field Template Injection in wake_cmd/shutdown_cmd
  3. May 26, 20266mo ago

    UpSnap 5.4.0 fixes initial setup takeover and command injection flaws

    UpSnap released version 5.4.0 with fixes for two security issues: an initial setup flaw that could let an attacker claim the first superuser account on an uninitialized instance, and a command injection issue in device IP and MAC fields that could lead to server-side code execution. The release changed first-superuser creation to a one-time PocketBase setup link shown in server console logs and added backend, database, and browser-side validation for IP and MAC values.

    Release 5.4.0 · seriousm4x/UpSnap · GitHub
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.