CVE-2026-39567
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 · uneditedUnauthenticated PHP Object Injection in Santé <= 1.5.1 versions.
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 confidenceUnauthenticated PHP Object Injection vulnerability in the Santé application versions 1.5.1 and below allows remote attackers to inject malicious PHP objects via unserialized user input without authentication, potentially leading to remote code execution depending on available classes in the application.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Identify Santé application installationLocate web application files by searching for directories or files containing 'sante', 'santé', or similar naming patterns in the web root directory.Affected if The Santé application files are present on the system.
-
Determine installed versionCheck for version files, changelogs, or configuration files within the Santé application directory that reveal the software version. Common locations include a VERSION file, composer.json, or the main index/bootstrap file.Affected if The installed version is 1.5.1 or lower.
-
Locate unserialize() calls in source codeSearch PHP source files in the application directory for the pattern 'unserialize(' to identify where user input is being deserialized without secure handling.Affected if Code contains unserialize() calls that process user-controlled input without sanitization.
-
Verify application is network accessibleConfirm the application is exposed on a network-accessible interface rather than localhost-only, as the vulnerability is exploitable remotely without authentication.Affected if The application is reachable over a network and accepts incoming requests.
A user is affected if the Santé application is installed, runs version 1.5.1 or below, contains unserialize() calls handling user input, and is network-accessible.
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 · scopedReplace unsafe unserialize() calls with secure alternatives like json_decode for data handling, or implement strict allowlist validation if deserialization is required; update to version 1.5.2 or later if available.
Latest version of Santé plugin (greater than 1.5.1)
- 1. Identify the exact version of the Santé plugin currently installed on the WordPress site
- 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- 3. Check the current version number displayed for the Santé plugin
- 4. If the installed version is 1.5.1 or lower, update to the latest available version from the WordPress plugin repository
- 5. Alternatively, navigate to Dashboard > Updates and check for any available updates for the Santé plugin
- 6. Before updating, ensure a complete backup of the WordPress site including database and files
- 7. After updating, verify the new version number and test critical functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39567 — 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-39567 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