Shinseiyo Sogo SoftApplication · Touki Kyoutaku Online

CVE-2023-27527

HIGH · 7.5 CVSS v3.1 Published 2023-05-10
Fix available
A fix is available. Upgrade to after 7.9a or later.
See remediation →
84/100
Remediation priority · High
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
Shinseiyo Sogo Soft (7.9A) and earlier improperly restricts XML external entity references (XXE). By processing a specially crafted XML file, arbitrary files on the PC may be accessed by an attacker.

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 confidence

Shinseiyo Sogo Soft versions 7.9A and earlier contains an XML External Entity (XXE) injection vulnerability. The application improperly restricts XML external entity references when processing XML files, allowing an attacker to craft malicious XML that references external entities to read arbitrary files from the server's filesystem.

MitigationDisable external entity processing in the XML parser configuration, implement input validation for XML files, and upgrade to a patched version if available from the vendor.

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
Shinseiyo Sogo SoftApplication
Affected:<= 7.9a

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

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

  1. Identify the installed version of Touki Kyoutaku Online Shinseiyo Sogo Soft
    Locate the application in your environment and check its version information. This is typically found in the software's about dialog, installation directory, or system inventory. Compare your version against the affected range: <= 7.9a
    Affected if The installed version is 7.9a or earlier (7.9A and versions below)
  2. Determine if XML file upload or processing functionality exists
    Identify whether the application has features that accept, parse, or process XML files. This may include XML import, configuration file loading, data interchange modules, or API endpoints that handle XML payloads. Review the application's feature documentation or enumerate accessible endpoints.
    Affected if The application processes XML files from users or external sources without restricting external entity references
  3. Check XML parser configuration for external entity settings
    If you have access to the application's configuration files or XML processing libraries, inspect the XML parser settings. Look for whether the parser is configured to allow external entity resolution or DTD processing. The specific configuration file or setting depends on the application's implementation.
    Affected if The XML parser has external entity processing enabled (not disabled)
  4. Verify network exposure of XML processing endpoints
    Determine if XML processing functionality is accessible over the network. This could include web services, APIs, or any network-accessible interface that accepts XML input. Document which endpoints accept XML content.
    Affected if XML processing functionality is exposed to network users or external systems

You are affected if the installed version is 7.9a or earlier AND the application has XML file processing capabilities exposed to users or external sources.

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.

From vendor data
Upgrade available Upgrade to a release after 7.9a
Interim mitigation

Disable external entity processing in the XML parser configuration, implement input validation for XML files, and upgrade to a patched version if available from the vendor.

Fix this in Shinseiyo Sogo Soft Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,960
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-27527 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-27527 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