dbcve.org
ProselfApplication · Northgrid

CVE-2023-39415

HIGH · 7.5 CVSS v3.1 Published 2023-08-18
Fix available
A fix is available. Upgrade to after 5.61 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
Improper authentication vulnerability in Proself Enterprise/Standard Edition Ver5.61 and earlier, Proself Gateway Edition Ver1.62 and earlier, and Proself Mail Sanitize Edition Ver1.07 and earlier allow a remote unauthenticated attacker to log in to the product's Control Panel and perform an unintended operation.

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

Improper authentication vulnerability in Proself file management products allows remote unauthenticated attackers to bypass authentication mechanisms and gain access to the Control Panel, enabling execution of unintended administrative operations.

MitigationUpgrade Proself to versions newer than Ver5.61 (Enterprise/Standard), Ver1.62 (Gateway), or Ver1.07 (Mail Sanitize) to patch the authentication bypass.

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.07<= 1.62<= 5.61

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 if Proself is installed
    Check for Proself processes running on the system, or look for Proself installation directories on the server.
    Affected if Proself file management software is found running or installed on the system
  2. Determine the installed Proself version
    Access the Proself administrative interface or check version information files within the Proself installation directory. The version is typically displayed in the Control Panel about section or in version-related configuration files.
    Affected if The installed version falls within the affected ranges: <= 5.61 (Enterprise/Standard), <= 1.62 (Gateway), or <= 1.07 (Mail Sanitize)
  3. Verify Control Panel accessibility
    Attempt to access the Proself Control Panel endpoint remotely without providing credentials. The vulnerability allows unauthenticated access to the Control Panel interface.
    Affected if The Control Panel is accessible remotely without authentication, indicating the bypass is present
  4. Check network exposure of the Control Panel
    Review firewall rules and network configuration to determine if the Proself Control Panel port is exposed to untrusted networks or the internet.
    Affected if The Control Panel port is exposed to external networks without proper access restrictions

A user is affected if they have Proself installed with version 5.61 or lower (Standard/Enterprise), 1.62 or lower (Gateway), or 1.07 or lower (Mail Sanitize), and the Control Panel is network-accessible to potential attackers.

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 a release after 5.61
Interim mitigation

Upgrade Proself to versions newer than Ver5.61 (Enterprise/Standard), Ver1.62 (Gateway), or Ver1.07 (Mail Sanitize) to patch the authentication bypass.

Recommended fix Moderate confidence

Latest version of Proself Enterprise/Standard Edition (beyond 5.61), Gateway Edition (beyond 1.62), or Mail Sanitize Edition (beyond 1.07) - obtain exact version from vendor's security advisory at www.proself.jp

  1. 1. Check the current installed version of Proself by accessing the Control Panel or checking system documentation
  2. 2. Obtain the latest version of Proself from the official vendor website (www.proself.jp)
  3. 3. Review the vendor's release notes and security advisory for CVE-2023-39415 to confirm the fixed version number
  4. 4. Create a complete backup of the current Proself installation including configuration files and data
  5. 5. Stop the Proself service before performing the upgrade
  6. 6. Follow the vendor's documented upgrade procedure for your specific Proself edition (Enterprise/Standard, Gateway, or Mail Sanitize)
  7. 7. After upgrading, verify that the service starts correctly and the Control Panel is accessible
  8. 8. Test that authentication is now properly enforced and the previously vulnerable authentication bypass is no longer exploitable
Caveat Review vendor release notes for potential breaking changes; test in non-production environment first

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

Fix this in Proself Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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