CVE-2024-27115
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 · uneditedA 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. This leads to the possibility of execution of code on the underlying system when the file is triggered. 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 confidenceAn unauthenticated file upload vulnerability in SO Planning allows attackers to upload executable files to a publicly accessible directory before any validation occurs. Since files are moved to a publicly accessible folder prior to verification, the uploaded malicious files can be triggered to achieve remote code execution on the underlying system.
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< 1.52.02CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Soplanning versionLocate the version file in the Soplanning installation directory or access the admin panel/version information page. Common locations include a version.php file or the administration interface.Affected if The installed version is any version prior to 1.52.02 (e.g., 1.52.00, 1.51.x, 1.50.x, etc.)
-
Verify file upload functionality is accessibleIdentify the upload endpoint in Soplanning. This is typically found in modules related to document management, file attachments, or user profile picture uploads. Attempt to access or identify the upload mechanism without authentication.Affected if The upload functionality is exposed without requiring authentication and accepts file uploads
-
Inspect upload directories for unexpected filesLocate the upload directories within the Soplanning installation. Search for recently created files with executable extensions (.php, .phtml, .php5, .php7, .asp, .jsp, .exe, .sh, .cgi) in publicly accessible folders.Affected if Executable or script files exist in upload directories that were not uploaded through legitimate means
-
Check web server configuration for upload folder exposureReview the web server configuration (Apache nginx, IIS) to determine if upload directories are configured to serve files from a publicly accessible web path. Verify if directory listing or direct file access is permitted for upload folders.Affected if Upload directories are mapped to a web-accessible path and the web server serves files from these directories without restriction
You are affected if the Soplanning version is below 1.52.02 AND the file upload feature is exposed without authentication, allowing potential remote code execution via malicious uploaded files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.52.02
Upgrade to version 1.52.02 or later. If immediate patching is not possible, restrict public access to upload directories and consider implementing web application firewall rules to block executable file uploads.
1.52.02
- Upgrade Soplanning to version 1.52.02 or later
- After upgrade, verify that file upload functionality properly validates file types before storage
- Confirm that uploaded files are no longer placed in publicly accessible web directories
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27115 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-27115 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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