dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-50644

HIGH · 8.6 CVSS v4.0 Published 2026-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable Zero-click 6 weeks old

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 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 accessed (by the attacker or another user). This issue was fixed in version 1.56.01.

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 contains a SQL injection vulnerability in the audit retention configuration. Users with parameters_all rights can inject malicious SQL commands through the audit configuration form, which are stored and executed when the audit functionality is accessed by any user. This allows authenticated attackers with administrative-level permissions to manipulate database queries.

MitigationUpgrade to SOPlanning version 1.56.01 or later. Additionally, apply the principle of least privilege by reviewing and restricting the parameters_all permission to only essential personnel.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Locate SOPlanning installation
    Identify the web root directory where SOPlanning is installed (commonly /var/www/html/soplanning, /www/html/soplanning, or similar). Check for the presence of the main SOPlanning PHP files such as index.php, planning.php, or a soplanning directory.
    Affected if SOPlanning is present on the system
  2. Determine installed SOPlanning version
    Open the file VERSION.txt or version.php in the SOPlanning installation directory, or access the application's About/Help page which typically displays the version number. Compare this version to 1.56.01.
    Affected if Installed version is below 1.56.01
  3. Identify users with parameters_all permission
    Access the SOPlanning admin panel and navigate to the User Management or Rights Configuration section. Look for users or roles that have the 'parameters_all' permission enabled. This permission grants access to the audit retention configuration.
    Affected if Any user account has the parameters_all permission granted
  4. Examine audit configuration storage
    If you have database access, query the soplanning configuration table (commonly named config or similar) for entries related to audit_retention or audit configuration settings. Check for any unexpected or suspicious SQL-like characters in stored values.
    Affected if Audit configuration contains suspicious stored values or the feature is accessible

User is affected if running SOPlanning version below 1.56.01 with any user account possessing the parameters_all permission, as the SQL injection can be triggered through the audit retention configuration form.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to SOPlanning version 1.56.01 or later. Additionally, apply the principle of least privilege by reviewing and restricting the parameters_all permission to only essential personnel.

Recommended fix High confidence

SOPlanning version 1.56.01 or later

  1. 1. Identify the current SOPlanning version by accessing the admin panel or checking version files
  2. 2. Create a complete backup of the SOPlanning database and application files
  3. 3. Download SOPlanning version 1.56.01 or the latest stable version from the official source (www.soplanning.org)
  4. 4. Consult the official upgrade documentation for version-specific upgrade procedures
  5. 5. Apply the upgrade following the standard upgrade process (typically involves replacing application files and running any database migrations)
  6. 6. Log in to the admin panel and navigate to the audit retention configuration settings
  7. 7. Verify that the audit configuration form properly sanitizes input and does not reflect unsanitized SQL characters
  8. 8. Confirm the upgrade was successful by checking the version number in the application
Caveat Review release notes between current version and 1.56.01 for any breaking changes or deprecated features

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

Have this fixed 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 help mitigating

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-2026-50644 — 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-2026-50644 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