CyberSecBulletin

SOPlanning vulnerabilities

We track 10 vulnerabilities in SOPlanning products. 10 are rated high or critical, and none are known to be exploited. The most recent was published on July 9, 2026.

10vulnerabilities
5critical
5high
0exploited
9.1average CVSS score

Latest SOPlanning vulnerabilities

  • 8.6 High severity

    SOPlanning: Improper Neutralization of Special Elements used in an SQL Command

    CVE-2026-50644SOPlanning

    SOPlanning is vulnerable to SQL injection in the audit retention configuration. An attacker holding parameters_all rights can inject SQL commands into the audit configuration form which is then saved. The execution is triggered when the audit functionality is

  • 8.7 High severity

    SOPlanning: Improper Neutralization of Special Elements used in an SQL Command

    CVE-2026-40546SOPlanning

    SOPlanning is vulnerable to SQL Injection across multiple endpoints and parameters. Attacker with low privileges can inject arbitrary SQL commands, potentially gaining full control over the database. This issue affects SOPlanning version 1.55 and below.

  • 8.8 High severity

    SOPlanning: Missing Authorization

    CVE-2026-40543SOPlanning

    SOPlanning does not enforce authorization for backup functionalities. An unauthenticated attacker can directly query backup-related endpoints and retrieve backup archives containing user databases with usernames and password hashes, as well as the config.csv f

  • 8.8 High severity

    SOPlanning: Incorrect Authorization

    CVE-2025-62730SOPlanning

    SOPlanning is vulnerable to Privilege Escalation in user management tab. Users with user_manage_team role are allowed to modify permissions of users. However, they are able to assign administrative permissions to any user including themselves. This allow a mal

  • 7.5 High severity

    SOPlanning: Generation of Predictable Numbers or Identifiers

    CVE-2025-62294SOPlanning

    SOPlanning is vulnerable to Predictable Generation of Password Recovery Token. Due to weak mechanism of generating recovery tokens, a malicious attacker is able to brute-force all possible values and takeover any account in reasonable amount of time. This issu

  • 9.8 Critical severity

    Soplanning: Unrestricted Upload of File with Dangerous Type

    CVE-2024-57169SOPlanning

    A file upload bypass vulnerability exists in SOPlanning 1.53.00, specifically in /process/upload.php. This vulnerability allows remote attackers to bypass upload restrictions and potentially achieve remote code execution by uploading malicious files.

  • 9.8 Critical severity

    SO Planning: Unrestricted Upload of File with Dangerous Type

    CVE-2024-27115Simple Online PlanningEPSS 4.63%

    A unauthenticated Remote Code Execution (RCE) vulnerability is found in the SO Planning online planning tool. With this vulnerability, an attacker can upload executable files that are moved to a publicly accessible folder before verifying any requirements. Thi

  • 9.8 Critical severity

    SO Planning: Time-of-check Time-of-use (TOCTOU) Race Condition

    CVE-2024-27114Simple Online Planning

    A unauthenticated Remote Code Execution (RCE) vulnerability is found in the SO Planning online planning tool. If the public view setting is enabled, a attacker can upload a PHP-file that will be available for execution for a few milliseconds before it is remov

  • 9.8 Critical severity

    SO Planning: Authorization Bypass Through User-Controlled Key

    CVE-2024-27113Simple Online Planning

    An unauthenticated Insecure Direct Object Reference (IDOR) to the database has been found in the SO Planning tool that occurs when the public view setting is enabled. An attacker could use this vulnerability to gain access to the underlying database by exporti

  • 9.8 Critical severity

    SO Planning: Improper Neutralization of Special Elements used in an SQL Command

    CVE-2024-27112Simple Online Planning

    A unauthenticated SQL Injection has been found in the SO Planning tool that occurs when the public view setting is enabled. An attacker could use this vulnerability to gain access to the underlying database. The vulnerability has been remediated in version 1.5