Skip to main content

NAVER MYBOX Explorer EUVDEUVD-2026-28530

| CVE-2026-8148 HIGH
Incorrect Privilege Assignment (CWE-266)
2026-05-08 naver GHSA-9r2v-r8jf-9prp
7.8
CVSS 3.1 · Vendor: naver
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain local user access
  2. Delivery
    Identify MYBOX Explorer installation
  3. Exploit
    Modify vulnerable registry keys
  4. Execution
    Trigger service/component restart
  5. Persist
    Execute code as NT AUTHORITY\SYSTEM
  6. Impact
    Establish persistence and control

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Privilege assignment review
Exploitation Conditions

Requires authenticated local access to a Windows system with NAVER MYBOX Explorer installed (versions before 3.0.11.160). Attacker must have low-privileged interactive logon credentials (standard user account) with sufficient permissions to modify specific registry keys - the vulnerability exists because these registry paths lack proper access controls. Exploitation does NOT require administrator privileges or non-default configurations, making any standard user installation vulnerable. The CVSS vector PR:L (low privileges required) and AC:L (low attack complexity) indicate exploitation is straightforward once local access is achieved. No user interaction (UI:N) is required beyond the attacker's own registry manipulation actions. Attack surface is limited to Windows platforms only, as indicated by the Microsoft tag and Windows-specific NT AUTHORITY\SYSTEM privilege context.

Impact

CVSS 7.8 indicates high severity with local access vector, low attack complexity, and requires low privileges without user interaction, achieving full impact across confidentiality, integrity, and availability. However, multiple signals suggest moderate real-world urgency. EPSS score of 0.02% (4th percentile) indicates extremely low probability of exploitation observed in the wild. The vulnerability is not in CISA KEV, confirming no known active exploitation. The attack vector limitation to local access significantly reduces exposure compared to network-exploitable vulnerabilities. Primary risk scenario involves post-compromise escalation where an attacker has already gained initial foothold through phishing, supply chain compromise, or other means. Organizations should prioritize patching on endpoints where NAVER MYBOX Explorer is deployed, especially in environments where users have local interactive access, but this does not warrant emergency response like remotely exploitable system-level vulnerabilities. The vendor has released a patch (version 3.0.11.160), reducing residual risk to update deployment logistics rather than unmitigated exposure.

Exploit ScenarioDerived

An attacker with limited user credentials on a Windows endpoint, potentially gained through phishing or credential theft, identifies NAVER MYBOX Explorer installation. The attacker manipulates specific registry keys associated with MYBOX Explorer services or startup configurations, injecting malicious code paths or parameters. When the MYBOX Explorer service or privileged component processes these registry entries at next service restart or scheduled execution, it runs the attacker-controlled code as NT AUTHORITY\SYSTEM, granting complete control over the Windows system including access to all user data, credential stores, and ability to disable security controls or establish persistence.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 08, 2026

Local attackers with standard user credentials can escalate privileges to NT AUTHORITY\SYSTEM in NAVER MYBOX Explorer for Windows through registry manipulation. The vulnerability affects versions prior to 3.0.11.160 and stems from improper privilege checks, allowing complete system control on compromised endpoints. EPSS risk is low at 0.02% (4th percentile), indicating minimal observed exploitation probability. No active exploitation has been reported and this vulnerability is not listed in CISA KEV.

RemediationAI

Upgrade NAVER MYBOX Explorer to version 3.0.11.160 or later, as confirmed by NAVER's security advisory at https://cve.naver.com/detail/cve-2026-8148.html. Organizations should prioritize endpoints where multiple users share systems or where users have interactive logon rights. If immediate patching is not feasible, implement compensating controls: restrict local user privileges through Windows User Account Control (UAC) enforcement and group policy to limit interactive logon rights to trusted administrators only, though this significantly impacts usability for legitimate MYBOX users. Monitor registry access to NAVER MYBOX Explorer paths using Windows Sysmon Event ID 13 (RegistryEvent) for unexpected modifications by non-SYSTEM accounts. Consider temporarily uninstalling MYBOX Explorer on high-value targets if business continuity permits alternative cloud storage solutions during patch deployment. Note that registry monitoring may generate high event volumes in production environments.

Affected VersionsENISA

NAVER MYBOX Explorer patch: 3.0.11.160

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

NAVER MYBOX Explorer is a cloud storage synchronization client for Windows. The vulnerability is rooted in CWE-266 (Incorrect Privilege Assignment), where the application fails to properly validate privilege boundaries when processing registry operations. Windows registry manipulation as a privilege escalation vector typically involves exploiting writable registry keys that control service behavior, scheduled tasks, or application startup parameters that execute with elevated privileges. The improper privilege checks allow a low-privileged user to modify registry entries that are subsequently processed by a higher-privileged component of MYBOX Explorer, resulting in code execution as NT AUTHORITY\SYSTEM - the highest privilege level on Windows systems.

Know when Naver Mybox Explorer gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (naver) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from Vendor (naver) · only source for this CVE.

CVSS VectorVendor: naver

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
CVSS changed
May 08, 2026 - 19:22 NVD
7.8 (HIGH)
CVE Published
May 08, 2026 - 04:36 nvd
HIGH 7.8
CVE Published
May 08, 2026 - 04:36 nvd
UNKNOWN (no severity yet)

DescriptionCVE.org

NAVER MYBOX Explorer for Windows before 3.0.11.160 allows a local attacker to escalate privileges to NT AUTHORITY\SYSTEM via registry manipulation due to improper privilege checks.

Executive ViewAI

Why It Matters

CVE-2026-8148 allows local users with standard Windows credentials to gain system-level privileges on NAVER MYBOX Explorer prior to version 3.0.11.160, enabling full endpoint compromise. This poses a material risk to organizations deploying MYBOX Explorer, particularly in environments where user access controls are not strictly enforced, as successful exploitation grants attackers complete system control to install malware, exfiltrate data, or persist across system rebuilds.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict NAVER MYBOX Explorer installation and execution to administrative accounts only; (2) Implement Windows AppLocker or similar application whitelisting to prevent unauthorized execution; (3) Monitor and restrict user-level registry write permissions to HKLM hives where feasible; (4) Deploy endpoint detection and response (EDR) tools configured to flag privilege escalation events; (5) Enforce principle of least privilege across user accounts to limit damage from successful local exploitation.

Threat Intelligence Overview

EPSS Score
0.0%
Top 96% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy