dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 24 Dec 2024.
ProselfApplication · Northgrid

CVE-2023-45727

HIGH · 7.5 CVSS v3.1 Published 2023-10-18
Fix available
A fix is available. Upgrade to 1.09 / 1.66 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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
Proself Enterprise/Standard Edition Ver5.62 and earlier, Proself Gateway Edition Ver1.65 and earlier, and Proself Mail Sanitize Edition Ver1.08 and earlier allow a remote unauthenticated attacker to conduct XML External Entity (XXE) attacks. By processing a specially crafted request containing malformed XML data, arbitrary files on the server containing account information may be read by the 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 · high confidence

Proself Enterprise, Standard, Gateway, and Mail Sanitize editions contain an XML External Entity (XXE) vulnerability in earlier versions. An unauthenticated remote attacker can send specially crafted malformed XML requests to the server, causing the XML parser to process external entity references that can be leveraged to read arbitrary files on the server including files containing account credentials.

MitigationUpgrade to the latest patched version of Proself (Enterprise/Standard Ver5.63 or later, Gateway Edition Ver1.66 or later, Mail Sanitize Edition Ver1.09 or later). Additionally, configure XML parsers to disable external entity processing as a defense-in-depth measure.

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
ProselfApplication
Affected:< 1.09< 1.66< 5.63

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 Proself edition and installed version
    Locate the Proself installation directory and check the version file or banner. Common locations: check for version.txt, about page in web interface, or installation logs. Note which edition (Standard/Enterprise, Gateway, or Mail Sanitize) is deployed.
    Affected if The installed version is below 5.63 for Standard/Enterprise, below 1.66 for Gateway, or below 1.09 for Mail Sanitize edition.
  2. Confirm XML processing is enabled
    Review the Proself configuration files (typically in conf/ or config/ directory) for XML-related settings. Check if XML upload or parsing features are enabled for file handling, document import, or API endpoints.
    Affected if XML processing functionality is active in the Proself configuration.
  3. Check XML parser security settings
    Examine the application server or Proself XML parser configuration for external entity processing settings. Look for parser configuration files that control XXE protection, such as XMLConstants or parser-specific config files.
    Affected if External entity processing is not explicitly disabled in the XML parser configuration, or the setting is unknown.
  4. Verify exposed XML endpoints
    Identify if Proself web interfaces or APIs accept XML uploads or process XML content. Check for endpoints that handle document imports, configuration uploads, or XML-based file operations.
    Affected if XML input acceptance is enabled on accessible web endpoints without XXE protection.

You are affected if running a Proself version below 5.63 (Standard/Enterprise), below 1.66 (Gateway), or below 1.09 (Mail Sanitize) AND XML processing with external entity support is enabled in your configuration.

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
Upgrade available Upgrade to 1.09 / 1.66 / 5.63 or later
Fixed in 1.091.665.63
Interim mitigation

Upgrade to the latest patched version of Proself (Enterprise/Standard Ver5.63 or later, Gateway Edition Ver1.66 or later, Mail Sanitize Edition Ver1.09 or later). Additionally, configure XML parsers to disable external entity processing as a defense-in-depth measure.

Recommended fix High confidence

Proself Enterprise/Standard: 5.63+; Gateway: 1.66+; Mail Sanitize: 1.09+

  1. Identify which Proself edition is in use (Enterprise/Standard, Gateway, or Mail Sanitize)
  2. Download the latest version of the applicable Proself edition from the official vendor website (www.proself.jp)
  3. Back up the current Proself configuration and data
  4. Stop the Proself service
  5. Install the new version (Enterprise/Standard: 5.63 or later; Gateway: 1.66 or later; Mail Sanitize: 1.09 or later)
  6. Restore the configuration backup if needed
  7. Start the Proself service
  8. Verify the installation and test functionality

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

Fix this in Proself Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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