CVE-2026-40543
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 · uneditedSOPlanning does not enforce authorization for backup functionalities. An unauthenticated attacker can directly query backup-related endpoints and retrieve backup archives containing user databases with usernames and password hashes, as well as the config.csv file, which includes additional sensitive information. 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 · high confidenceSOPlanning versions 1.55 and below lack authorization enforcement on backup-related endpoints, allowing any unauthenticated attacker to directly download backup archives. These archives contain the user database with plaintext usernames and password hashes, plus the config.csv file with additional sensitive configuration data.
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
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SOPlanning installation and versionLocate the SOPlanning installation directory and check the version file (commonly version.php, info.php, or the main index.php header) to determine the installed version numberAffected if The installed version is 1.55 or lower
-
Locate backup directory or endpointSearch for common backup-related paths such as /backup/, /download_backup.php, /export/, or similar endpoints in the web root. Check the application configuration or source code for backup-related PHP filesAffected if Backup-related directories or scripts exist in the web-accessible path
-
Test backup endpoint accessibility without authenticationUsing a web browser or curl tool, attempt to access suspected backup endpoints (e.g., /backup/, /download_backup.php, /export/backup) WITHOUT providing any login credentialsAffected if The backup endpoint returns a successful response (200 OK) without requiring authentication
-
Verify backup file contents are exposedIf backup endpoints are accessible, check if backup archives (zip, tar, gz files) can be downloaded directly. Inspect whether the response includes database dumps or config.csv containing plaintext credentialsAffected if Backup archives containing config.csv or database files are downloadable without authentication
If SOPlanning version 1.55 or below is installed AND backup endpoints or files are accessible without any authentication, the environment is affected by this CVE.
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.
From vendor dataImplement and enforce role-based authorization checks on all backup endpoints to ensure only authenticated, authorized administrators can access backup functionality. Consider disabling or restricting backup endpoints from unauthenticated network access as an immediate workaround.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-40543 — 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-2026-40543 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