CVE-2025-64772
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 · uneditedThe installer of INZONE Hub 1.0.10.3 to 1.0.17.0 contains an issue with the DLL search path, which may lead to insecurely loading Dynamic Link Libraries. As a result, arbitrary code may be executed with the privilege of the user invoking the installer.
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 · moderate confidenceThe INZONE Hub installer versions 1.0.10.3 through 1.0.17.0 contains a DLL search path vulnerability (DLL hijacking). The installer insecurely loads Dynamic Link Libraries, potentially allowing an attacker to place a malicious DLL in a location where the installer will load it, resulting in arbitrary code execution with the privileges of the user running the installer.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Locate INZONE Hub installationCheck for INZONE Hub in the Windows Start Menu, or navigate to typical installation directories such as C:\Program Files\Sony\INZONE Hub or C:\Program Files (x86)\Sony\INZONE HubAffected if INZONE Hub is not found on the system (not affected)
-
Identify installed version via file propertiesRight-click the INZONE Hub executable (INZONE Hub.exe) in the installation folder, select Properties, and view the File version on the Details tabAffected if The displayed version falls within the range 1.0.10.3 to 1.0.17.0 inclusive
-
Identify version via Windows Programs and FeaturesOpen Control Panel > Programs and Features (or Settings > Apps), locate INZONE Hub in the list, and note the version shownAffected if The listed version falls within the range 1.0.10.3 to 1.0.17.0 inclusive
-
Check installer version if installer file is availableIf you have the INZONE Hub installer file (.exe), right-click it, select Properties, and view the Details tab for the version informationAffected if The installer version falls within the range 1.0.10.3 to 1.0.17.0 inclusive
A user is affected if the installed INZONE Hub application or the installer they intend to use has a version between 1.0.10.3 and 1.0.17.0 inclusive.
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.
From vendor dataUntil an official vendor patch is released, avoid running the INZONE Hub installer from directories with untrusted content, and ensure the installer is run from a trusted location. Users should update to a patched version once available.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64772 — 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-64772 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