dbcve.org
SoplanningApplication

CVE-2020-13963

CRITICAL · 9.8 CVSS v3.1 Published 2021-03-21
Fix available
A fix is available. Upgrade to 1.47 or later.
See remediation →
100/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
SOPlanning before 1.47 has Incorrect Access Control because certain secret key information, and the related authentication algorithm, is public. The key for admin is hardcoded in the installation code, and there is no key for publicsp (which is a guest account).

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

SOPlanning before version 1.47 contains an incorrect access control vulnerability where secret authentication keys are hardcoded in the installation code. The admin account uses a hardcoded key that is publicly known, and the publicsp guest account has no password protection at all, allowing unauthenticated or improperly authenticated access.

MitigationUpgrade to SOPlanning 1.47 or later, change all default/hardcoded keys to unique, strong values, and disable or properly secure the guest (publicsp) account.

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
SoplanningApplication
Affected:>= 1.45, < 1.47

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

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

  1. Check the installed SOPlanning version
    Locate the version file or header in the SOPlanning installation directory (commonly version.php, or check the main index.php for a version string) and note the exact version number
    Affected if The installed version is 1.45, 1.46, or any version >= 1.45 but < 1.47
  2. Inspect installation code for hardcoded authentication keys
    Search the source files (particularly configuration or initialization files like config.php, inc/*.php, or similar) for hardcoded password or key strings related to admin authentication
    Affected if Hardcoded password or key values are found in the source code or configuration files
  3. Verify admin account access with known default credentials
    Attempt to log into the admin account using publicly known default credentials associated with this CVE (the hardcoded key mentioned in the vulnerability disclosure)
    Affected if Login succeeds with default or hardcoded admin credentials, confirming the vulnerability is present
  4. Check if publicsp guest account is accessible without authentication
    Attempt to access the system using the 'publicsp' username with no password, or check if guest/super user access is enabled in the user configuration
    Affected if The publicsp guest account exists and grants access without any password or with an empty password
  5. Examine user configuration for hardcoded or default passwords
    Review the user management configuration files or database user table for accounts with hardcoded, default, or missing passwords (particularly admin and publicsp accounts)
    Affected if Default or hardcoded passwords are found in user configurations, or the publicsp account has no password protection enabled

A user is affected if SOPlanning version is >= 1.45 and < 1.47 AND (hardcoded admin credentials are present in the installation OR the publicsp guest account has no password protection).

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.47 or later
Fixed in 1.47
Interim mitigation

Upgrade to SOPlanning 1.47 or later, change all default/hardcoded keys to unique, strong values, and disable or properly secure the guest (publicsp) account.

Recommended fix High confidence

Soplanning 1.47 or later

  1. 1. Backup the current Soplanning installation and database before proceeding with the upgrade
  2. 2. Download Soplanning version 1.47 or later from the official Soplanning website (forum.soplanning.org)
  3. 3. Extract the downloaded files and replace the existing Soplanning files on the server
  4. 4. Run the database upgrade script if provided with the new version
  5. 5. Verify the installation by logging in and checking that the hardcoded credentials vulnerability has been addressed
  6. 6. If available, change any default credentials and ensure no hardcoded keys remain in the installation code

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

Fix this in Soplanning Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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