dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-40544

MEDIUM · 5.1 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 →
55/100
Remediation priority · Elevated
Remotely reachable

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 Stored Cross-Site Scripting (XSS) via /process/upload_backup endpoint. An authenticated attacker with access to the backup functionality can upload a crafted ZIP archive containing a malicious user.csv file with embedded JavaScript. The injected code is executed in the victim’s browser when a user clicks the Edit button for the malicious backup. 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 stored XSS vulnerability in the /process/upload_backup endpoint. An authenticated attacker with backup functionality access can upload a ZIP archive containing a malicious user.csv file with embedded JavaScript. The payload executes when a victim views or clicks Edit on the crafted backup entry.

MitigationImplement strict input validation and sanitization on CSV file contents during backup import/extraction, and apply contextual output encoding when rendering backup data in the Edit interface to prevent XSS execution.

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
Low
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N/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 version
    Locate the SOPlanning installation and determine its version number. Check version file, about page, or admin interface for the installed version string.
    Affected if The installed version is 1.55 or lower.
  2. Verify backup functionality is accessible
    Confirm the authenticated user account has access to the backup upload/restore feature. Check user permissions or role settings within SOPlanning admin panel.
    Affected if The user account has backup functionality access.
  3. Confirm upload_backup endpoint exists
    Check if the /process/upload_backup endpoint is accessible and functional in the SOPlanning web application.
    Affected if The endpoint exists and accepts file uploads.
  4. Verify backup Edit interface exists
    Check if the backup management interface includes an Edit button or equivalent function for viewing/editing uploaded backup metadata.
    Affected if The Edit button functionality for backups is present.
  5. Check CSV processing in backup restore
    Inspect whether SOPlanning parses and displays CSV file contents during the backup upload/restore process.
    Affected if The system reads and displays CSV data from uploaded ZIP archives.

A SOPlanning installation version 1.55 or below where an authenticated user with backup access can upload ZIP files containing CSV data that gets displayed via an Edit button is vulnerable to CVE-2026-40544.

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 CSV file contents during backup import/extraction, and apply contextual output encoding when rendering backup data in the Edit interface to prevent XSS execution.

Recommended fix Moderate confidence

SOPlanning version above 1.55 (latest stable release)

  1. 1. Ensure you have a complete backup of your SOPlanning installation and database before proceeding.
  2. 2. Download the latest version of SOPlanning from the official vendor website (www.soplanning.org).
  3. 3. Review the release notes for the newer version to confirm the XSS vulnerability fix is included.
  4. 4. Upload and install the new version, following the vendor's standard upgrade procedure.
  5. 5. After upgrading, verify that the /process/upload_backup endpoint now properly sanitizes CSV file contents.
  6. 6. As a precautionary config mitigation, restrict backup functionality to only highly trusted administrators.
  7. 7. Test the backup upload feature with a sample CSV to confirm the fix works correctly.
Caveat Review upgrade notes for any changes to backup/restore functionality or PHP version requirements

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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