dbcve.org
XML External Entity (XXE)Weakness · CWE-611

CVE-2025-27523

HIGH · 8.7 CVSS v3.1 Published 2025-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges 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
XXE vulnerability in Hitachi JP1/IT Desktop Management 2 - Smart Device Manager on Windows.This issue affects JP1/IT Desktop Management 2 - Smart Device Manager: from 12-00 before 12-00-08, from 11-10 through 11-10-08, from 11-00 through 11-00-05, from 10-50 through 10-50-06.

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

This is an XML External Entity (XXE) vulnerability in Hitachi JP1/IT Desktop Management 2 - Smart Device Manager on Windows. XXE vulnerabilities allow attackers to inject malicious XML containing external entity references, potentially enabling disclosure of internal files, SSRF attacks, or denial of service by exploiting how the application parses XML input.

MitigationApply the vendor-provided patches: upgrade to version 12-00-08, 11-10-08, 11-00-05, or 10-50-06 (or later versions) to disable external entity processing in the XML parser.

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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/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. Verify Hitachi JP1/IT Desktop Management 2 is installed
    Open Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell to list installed software. Look for 'Hitachi JP1/IT Desktop Management 2' or 'IT Desktop Management 2' in the list.
    Affected if The product is not found in installed programs, indicating it is not present.
  2. Find the Smart Device Manager version
    Navigate to the installation directory (commonly C:\Program Files\Hitachi\JP1ITDM2\ or C:\Hitachi\JP1ITDM2\). Look for a version file, or check the application executable properties (right-click on SDM.exe or similar binary > Properties > Details tab).
    Affected if The version cannot be determined or is older than the versions receiving fixes.
  3. Confirm the Smart Device Manager service is running
    Open Services (services.msc) and locate the 'JP1/IT Desktop Management 2 Smart Device Manager' service. Verify its status is Running, or run 'Get-Service *ITDM*' in PowerShell.
    Affected if The service is not installed or not running - the XXE flaw requires the application to be operational.
  4. Check if the web management interface is accessible
    Open a browser and attempt to access the Smart Device Manager web portal (commonly https://localhost:8443/sdm or http://localhost:8080/sdm). Check the application's configuration files (such as server.xml or web.xml in the conf folder) for the configured HTTP/HTTPS port.
    Affected if The web interface is accessible on a network-facing IP, increasing exposure to external attackers.
  5. Identify XML input points in the application
    Log into the Smart Device Manager web interface and navigate through device import, configuration backup/restore, or API integration features. These often process XML files. Review any logs in the 'logs' folder for XXE-related error messages.
    Affected if XML import or processing features are available and enabled, providing the attack vector for XXE exploitation.

You are affected if Hitachi JP1/IT Desktop Management 2 Smart Device Manager is installed, running, and your version is older than the patched releases while the web interface with XML processing features is accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided patches: upgrade to version 12-00-08, 11-10-08, 11-00-05, or 10-50-06 (or later versions) to disable external entity processing in the XML parser.

Recommended fix High confidence

Version 12-00-08 (or later), 11-10-08 (or later), 11-00-05 (or later), or 10-50-06 (or later) depending on your current version branch

  1. 1. Identify the currently installed version of JP1/IT Desktop Management 2 - Smart Device Manager from the application or system information.
  2. 2. Determine which version branch (12-00, 11-10, 11-00, or 10-50) your installation belongs to.
  3. 3. Access the Hitachi support portal at www.hitachi.com and locate the download page for JP1/IT Desktop Management 2 - Smart Device Manager.
  4. 4. Download the appropriate patched version for your branch: upgrade to version 12-00-08 or later for the 12-00 branch, 11-10-08 or later for the 11-10 branch, 11-00-05 or later for the 11-00 branch, or 10-50-06 or later for the 10-50 branch.
  5. 5. Back up the current installation and configuration data before applying the upgrade.
  6. 6. Install the patched version following the vendor's standard upgrade procedure for JP1/IT Desktop Management 2 - Smart Device Manager.
  7. 7. Verify the installation completed successfully and confirm the new version number.
  8. 8. Test that critical functionality of JP1/IT Desktop Management 2 - Smart Device Manager continues to operate normally after the upgrade.
Caveat Review Hitachi release notes for your version branch to check for any compatibility or configuration changes between versions

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27523 — 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-27523 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