CVE-2025-58323
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 · uneditedNAVER MYBOX Explorer for Windows before 3.0.8.133 allows a local attacker to escalate privileges to NT AUTHORITY\SYSTEM by executing arbitrary files 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 confidenceNAVER MYBOX Explorer for Windows versions prior to 3.0.8.133 contain a local privilege escalation vulnerability where improper privilege checks allow a local attacker to execute arbitrary files with NT AUTHORITY\SYSTEM privileges, achieving full system compromise.
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< 3.0.8.133CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Verify NAVER MYBOX Explorer is installedCheck the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Naver Mybox' or 'NAVER MYBOX Explorer', or look for the program in Add/Remove ProgramsAffected if The software is found in the system
-
Identify the installed version numberLocate the Mybox installation directory (typically C:\Program Files\Naver\Mybox or C:\Users\%USERNAME%\AppData\Local\Programs\Mybox) and right-click the Mybox.exe file to view Properties, or query the registry Uninstall key for the DisplayVersion valueAffected if A version number is retrieved that is lower than 3.0.8.133
-
Confirm the version is within vulnerable rangeCompare the identified version to 3.0.8.133 using numeric or string comparison (for example, 3.0.8.132, 3.0.7.x, or any 3.0.x version below 3.0.8.133)Affected if The installed version is less than 3.0.8.133
-
Verify the service or component runs with elevated privilegesOpen Services.msc and look for a Naver Mybox service, or check Task Manager for Mybox processes running under the SYSTEM account or as a scheduled task with elevated permissionsAffected if A Mybox service or process runs with NT AUTHORITY\SYSTEM or elevated privileges
If NAVER MYBOX Explorer is installed and the version is below 3.0.8.133, the system is affected by this local privilege escalation vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.0.8.133
Upgrade NAVER MYBOX Explorer to version 3.0.8.133 or later to obtain the vendor patch addressing the improper privilege checks.
3.0.8.133 or later
- Download the latest version of NAVER MYBOX Explorer for Windows from the official vendor website
- Close any running instances of MYBOX Explorer
- Install version 3.0.8.133 or later by running the installer with appropriate administrator privileges if needed
- Verify the installed version is 3.0.8.133 or higher to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58323 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-58323 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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