dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-40548

MEDIUM · 6.4 CVSS v4.0 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable 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
SOPlanning does not verify uploaded file extension. An authenticated attacker with access to the backup functionality can upload a crafted ZIP archive containing a legitimate user.csv file alongside a malicious file, which is extracted on the server. When combined with CVE-2026-40547 (Path Traversal), the malicious file (e.g., a PHP script) can be placed in a web-accessible location and executed via the browser. This issue affects SOPlanning version 1.55 and below.

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 · moderate confidence

SOPlanning fails to validate file extensions on uploads within its backup functionality. An authenticated attacker can upload a crafted ZIP archive containing both a legitimate user.csv file and a malicious file. When extracted on the server and combined with the path traversal vulnerability (CVE-2026-40547), the malicious file can be placed in a web-accessible directory and executed for RCE.

MitigationImplement strict file extension allowlist validation for uploads and validate ZIP archive contents before extraction. Restrict backup functionality access to trusted users and upgrade to version 1.55+ where available.

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:N/VI:L/VA:N/SC:H/SI:H/SA:H/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. Identify SOPlanning installation and version
    Locate the SOPlanning application directory and check the version file (typically version.php, changelog.txt, or similar in the root directory). Common paths include /soplanning, /var/www/soplanning, or within the web document root.
    Affected if The installed version matches the affected range and you cannot determine that a security patch has been applied.
  2. Verify backup functionality is accessible
    Check if the backup/restore feature is enabled in the SOPlanning configuration. Look for backup-related PHP files in the /tools, /admin, or /include directories. Verify the feature is accessible to authenticated users.
    Affected if The backup upload functionality exists and is accessible to authenticated users without additional access controls.
  3. Inspect upload validation logic
    Examine the PHP code handling file uploads in the backup functionality. Look for functions that validate file extensions, MIME types, or file content before allowing upload. Search for $_FILES handling in backup-related PHP files.
    Affected if No file extension allow-listing or content-type validation is performed on uploaded files, or the validation can be bypassed.
  4. Check file storage location
    Identify where uploaded backup files are stored. Review the code that handles ZIP extraction and file placement. Determine if files are stored within the web document root.
    Affected if Uploaded files are extracted and stored in a web-accessible directory (within the document root).
  5. Confirm path traversal protection status
    Examine the ZIP extraction code for path traversal vulnerabilities (CVE-2026-40547). Look for insufficient sanitization of file paths within ZIP archives that could allow .. sequences to escape the intended directory.
    Affected if The ZIP extraction does not properly sanitize file paths, allowing attackers to write files outside the intended directory.

Your environment is affected if you run a vulnerable version of SOPlanning with the backup feature accessible to authenticated users, where uploaded ZIP files are not properly validated for extensions and can be extracted to web-accessible directories.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict file extension allowlist validation for uploads and validate ZIP archive contents before extraction. Restrict backup functionality access to trusted users and upgrade to version 1.55+ where available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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