dbcve.org
SoplanningApplication

CVE-2024-27114

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
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 removed, leading to execution of code on the underlying system. 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 remote code execution vulnerability exists in SO Planning when the public view setting is enabled. Attackers can upload a malicious PHP file that executes briefly (milliseconds) before being automatically removed, allowing arbitrary code execution on the underlying system.

MitigationUpdate SO Planning to version 1.52.02 or later. As an interim measure, disable the public view setting if not required, and restrict network access to the application until the patch can be applied.

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. Check Soplanning version
    Locate the version file typically found in the application root or check the admin panel for the installed Soplanning version number
    Affected if The installed version is lower than 1.52.02
  2. Verify public view setting status
    Access the Soplanning administrative configuration panel and navigate to the public view or visibility settings to determine if this feature is currently enabled
    Affected if The public view setting is enabled in the configuration
  3. Inspect upload directory for unexpected PHP files
    Check the designated upload directory (commonly /files/ or /upload/ within the Soplanning installation) for any unexpected or recently created PHP files that may indicate exploitation attempts
    Affected if Unexpected PHP files are present in upload directories
  4. Review web server access logs for upload activity
    Examine web server access logs for POST requests to upload endpoints, particularly those involving PHP file extensions occurring in short bursts
    Affected if Logs show suspicious upload activity involving PHP files

A system is affected if it runs Soplanning version below 1.52.02 with the public view setting enabled, as this combination allows unauthenticated attackers to upload and execute malicious PHP code.

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

Update SO Planning to version 1.52.02 or later. As an interim measure, disable the public view setting if not required, and restrict network access to the application until the patch can be applied.

Recommended fix High confidence

1.52.02

  1. 1. Create a complete backup of the current Soplanning installation directory and database
  2. 2. Download Soplanning version 1.52.02 from the official vendor website
  3. 3. Extract the new version files
  4. 4. Replace the existing Soplanning files with the new version 1.52.02 files
  5. 5. Restore any custom configuration files from the backup if needed
  6. 6. Verify the application is accessible and functioning correctly
  7. 7. Review the 'public view' setting configuration to ensure it is only enabled if business requirements demand it
  8. 8. Confirm the version number displays as 1.52.02 in the application admin interface

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
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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