dbcve.org
MyboxApplication · Navercorp

CVE-2025-58322

HIGH · 7.8 CVSS v3.1 Published 2025-08-28
Fix available
A fix is available. Upgrade to 3.0.8.133 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NAVER MYBOX Explorer for Windows before 3.0.8.133 allows a local attacker to escalate privileges to NT AUTHORITY\SYSTEM by invoking arbitrary DLLs due to improper privilege checks.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

NAVER MYBOX Explorer for Windows versions prior to 3.0.8.133 contains a local privilege escalation vulnerability where improper privilege checks allow a local attacker to load and execute arbitrary DLLs, achieving NT AUTHORITY\SYSTEM privileges.

MitigationUpdate to NAVER MYBOX Explorer version 3.0.8.133 or later. In the interim, restrict write access to the application directory and monitor for suspicious DLL loading activity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MyboxApplication
Affected:< 3.0.8.133

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if NAVER MYBOX Explorer is installed
    Check for the presence of the application in Program Files or Program Files (x86), typically under C:\Program Files\NAVER\MYBOX Explorer or C:\Program Files (x86)\NAVER\MYBOX Explorer. Also check the Start Menu for the application.
    Affected if The application is installed on the system.
  2. Determine the installed version of NAVER MYBOX Explorer
    Right-click on the MYBOX Explorer executable (usually named MyBoxExplorer.exe), select Properties, then go to the Details tab to view the File Version. Alternatively, open the application and check About or Settings for the version information.
    Affected if The installed version is lower than 3.0.8.133.
  3. Verify DLL search order hijacking risk
    Examine the permissions on the application directory (typically C:\Program Files\NAVER\MYBOX Explorer). Check if standard users have Write or Modify permissions to this directory by right-clicking the folder, selecting Properties, then Security tab.
    Affected if Users with limited privileges can write to the application directory, allowing placement of malicious DLLs that the application will load.
  4. Inspect application behavior for DLL loading
    Use Process Monitor or a similar tool to observe which DLLs MYBOX Explorer loads at startup. Compare the application's expected DLL paths against what is actually being loaded, noting any DLLs loaded from writable locations.
    Affected if The application loads DLLs from directories where unprivileged users have write access, indicating vulnerability to DLL hijacking.

The system is affected if NAVER MYBOX Explorer is installed with a version lower than 3.0.8.133 and the application directory or a writable location is in the DLL search path, allowing an unprivileged user to place and execute a malicious DLL for privilege escalation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.0.8.133 or later
Fixed in 3.0.8.133
Interim mitigation

Update to NAVER MYBOX Explorer version 3.0.8.133 or later. In the interim, restrict write access to the application directory and monitor for suspicious DLL loading activity.

Recommended fix Moderate confidence

3.0.8.133 or later

  1. Close any running instances of NAVER MYBOX Explorer
  2. Download the latest version of NAVER MYBOX Explorer (version 3.0.8.133 or later) from the official vendor source
  3. Run the installer or update package for the new version
  4. Follow the on-screen prompts to complete the installation or upgrade
  5. Verify that the installed version is 3.0.8.133 or later by checking the application's version information

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mybox Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58322 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58322 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data