dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-40547

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 is vulnerable to Path Traversal in backup endpoints. Authenticated remote attacker is able to exploit a vulnerable endpoint and construct payloads that allow reading and executing files previously added through the backup functionality. Critically, due to CVE-2026-40543 (Missing Authorization), any backup file can be read by any (unauthorized) user. 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 versions 1.55 and below contain a Path Traversal vulnerability in backup endpoints. An authenticated attacker can craft payloads to read and execute files that were previously added through the backup functionality. Combined with CVE-2026-40543 (Missing Authorization), unauthenticated users can also read any backup file.

MitigationImplement strict input validation and sanitization on backup endpoints to prevent path traversal sequences (../). Additionally, implement proper authorization checks to ensure users can only access backup files they are permitted to access.

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:L/VI:N/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. Locate SOPlanning installation and version
    Check your web application directory for SOPlanning. Look for a version file (often named version.php, VERSION.txt, or displayed in the application footer/admin panel). If using a package manager, run: composer show soplanning/soplanning or check your package-lock.json for the installed version.
    Affected if Version is 1.55 or below (the affected range)
  2. Verify backup functionality is enabled
    Check the SOPlanning configuration file (commonly config.php or settings.inc.php in the application root) for backup-related settings. Look for parameters like 'enable_backup', 'backup_enabled', or similar flags. Also check if the 'backup' directory exists under the web root.
    Affected if Backup functionality is enabled in configuration, making the vulnerable endpoints active
  3. Identify accessible backup endpoints
    Check for backup-related PHP files in the web directory, typically under paths like /backup/, /export/, or /tool/ directories. Common files include backup.php, export.php, or download.php. Review your web server access logs for requests to these endpoints.
    Affected if Backup endpoints are accessible without proper path validation or authentication

You are affected if SOPlanning version 1.55 or below is running with backup functionality enabled and the backup endpoints are accessible, regardless of authentication status due to the compounding authorization flaw.

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

Implement strict input validation and sanitization on backup endpoints to prevent path traversal sequences (../). Additionally, implement proper authorization checks to ensure users can only access backup files they are permitted to access.

Recommended fix Moderate confidence

SOPlanning version 1.56 or later (verify fixed version from vendor release notes)

  1. 1. Identify the current SOPlanning version in use by accessing the application or checking system documentation.
  2. 2. Obtain the latest stable version of SOPlanning from the official vendor website (www.soplanning.org) or trusted distribution channels.
  3. 3. Review the release notes for versions after 1.55 to confirm the patch includes fixes for CVE-2026-40547 (Path Traversal) and CVE-2026-40543 (Missing Authorization).
  4. 4. Create a complete backup of the current SOPlanning installation including database and configuration files.
  5. 5. Test the new version in a staging environment to verify functionality and identify any compatibility issues.
  6. 6. Deploy the updated version to production during a planned maintenance window.
  7. 7. After upgrade, verify the backup endpoint no longer allows path traversal by testing with controlled payloads (if authorized penetration testing was previously conducted).
  8. 8. Review access controls to ensure the authorization fix from CVE-2026-40543 is properly functioning.
Caveat Review release notes for potential breaking changes between 1.55 and the target version; test thoroughly in staging

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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