CVE-2025-10314
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 · uneditedIncorrect Default Permissions vulnerability in Mitsubishi Electric Corporation FREQSHIP-mini for Windows versions 8.0.0 to 8.0.2 allows a local attacker to execute arbitrary code with system privileges by replacing service executable files (EXE) or DLLs in the installation directory with specially crafted files. As a result, the attacker may be able to disclose, tamper with, delete, or destroy information stored on the PC where the affected product is installed, or cause a Denial of Service (DoS) condition on the affected system.
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 confidenceThis is a local privilege escalation vulnerability where the FREQSHIP-mini Windows service installation directory has overly permissive file access controls. An unprivileged local attacker can replace service executable files or DLLs with malicious counterparts, causing the service (running with system privileges) to execute attacker-controlled code upon service restart or reboot.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Verify FREQSHIP-mini installation existsSearch for FREQSHIP-mini in the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, or look for a FREQSHIP-mini folder under C:\Program Files or C:\Program Files (x86)Affected if FREQSHIP-mini software is installed on the system
-
Check installed version numberRight-click the main FREQSHIP-mini executable in the installation directory, select Properties, and view the Product version or File version on the Details tabAffected if The installed version is 8.0.0, 8.0.1, or 8.0.2
-
Locate the installation directory pathFrom the identified FREQSHIP-mini executable, note the full path shown in the Properties window under the General tab or the Shortcut tabAffected if The installation directory path is identified
-
Inspect file system permissions on installation folderRight-click the installation folder, select Properties, go to the Security tab, and check the permissions for Users, Everyone, or Authenticated Users groupsAffected if Users or Everyone group has Write or Modify permissions on the installation directory
-
Identify service executables in installation directoryOpen Services console (services.msc), look for any FREQSHIP-mini services, note their executable paths, and verify if they point to files within the installation directoryAffected if Windows services are configured to run executables from the installation directory with weak permissions
A user is affected if FREQSHIP-mini version 8.0.0-8.0.2 is installed with service executables located in a directory that allows non-admin users to modify files.
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 · scopedRestrict file system permissions on the FREQSHIP-mini installation directory to prevent non-privileged users from modifying or replacing service executables and DLLs. Apply the principle of least privilege, granting write/modify access only to administrators and the service account.
FREQSHIP-mini version 8.0.3 or later
- 1. Identify the current installed version of FREQSHIP-mini by checking the program's version information in Windows Control Panel or the installation directory
- 2. If the current version is 8.0.0, 8.0.1, or 8.0.2, plan for an upgrade to a fixed version
- 3. Backup all critical data and configuration files associated with FREQSHIP-mini before proceeding with the upgrade
- 4. Obtain the latest fixed version of FREQSHIP-mini from the official Mitsubishi Electric download page or contact their technical support
- 5. Uninstall the current vulnerable version of FREQSHIP-mini through Windows Control Panel > Programs and Features
- 6. Install the new fixed version of FREQSHIP-mini
- 7. Verify that the file permissions on the installation directory are correctly set after installation (only administrators should have write access to service executables and DLLs)
- 8. Restart any affected services if prompted and verify the application functions correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10314 — 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-10314 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