dbcve.org
SoplanningApplication

CVE-2024-27113

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-11
Fix available
A fix is available. Upgrade to 1.52.02 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
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 exporting it as a CSV file. The vulnerability has been remediated in version 1.52.02.

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

An unauthenticated IDOR vulnerability in the SO Planning tool allows attackers to access and export the underlying database as a CSV file when the public view setting is enabled. The vulnerability stems from improper direct object reference validation, enabling unauthorized database access without any authentication.

MitigationUpgrade to version 1.52.02 where the vulnerability has been remediated. Additionally, disable the public view setting as a defensive measure until the upgrade can be completed.

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.52.02

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. Identify installed Soplanning version
    Locate the version number in the application footer, admin panel, or version file typically found in the application root directory
    Affected if The installed version is earlier than 1.52.02
  2. Verify public view setting status
    Access the application administration panel and navigate to settings or configuration options to check whether the public view feature is enabled
    Affected if Public view is currently turned on or enabled
  3. Confirm unauthenticated access to export function
    Test accessing the CSV export endpoint directly without authentication by attempting a request to the suspected export URI (commonly /export.php, /export_csv.php, or similar)
    Affected if The export function responds without requiring login credentials
  4. Check for exposed database export capability
    Attempt to trigger a full database export through the public view interface or direct endpoint reference, observing if the entire database contents are returned as CSV data
    Affected if The system returns or allows downloading a complete database export without any access control enforcement

A defender is affected if running Soplanning version prior to 1.52.02 AND the public view setting is enabled, allowing unauthenticated users to export the entire database via direct reference.

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.52.02 or later
Fixed in 1.52.02
Interim mitigation

Upgrade to version 1.52.02 where the vulnerability has been remediated. Additionally, disable the public view setting as a defensive measure until the upgrade can be completed.

Recommended fix High confidence

1.52.02

  1. 1. Back up your current Soplanning installation and database before upgrading.
  2. 2. Download Soplanning version 1.52.02 from the official source (https://www.soplanning.org or your distribution channel).
  3. 3. Extract the new version files and replace the existing installation files.
  4. 4. Verify that the public view setting is configured appropriately after upgrade.
  5. 5. Test that the IDOR vulnerability is no longer exploitable by attempting unauthorized database exports.

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

Fix this in Soplanning Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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