dbcve.org
SpipApplication

CVE-2026-27475

HIGH · 8.1 CVSS v3.1 Published 2026-02-19
Fix available
A fix is available. Upgrade to 4.4.9 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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
SPIP before 4.4.9 allows Insecure Deserialization in the public area through the table_valeur filter and the DATA iterator, which accept serialized data. An attacker who can place malicious serialized content (a pre-condition requiring prior access or another vulnerability) can trigger arbitrary object instantiation and potentially achieve code execution. The use of serialized data in these components has been deprecated and will be removed in SPIP 5. This vulnerability is not mitigated by the SPIP security screen.

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 confidence

SPIP before 4.4.9 contains an insecure deserialization vulnerability in the public area via the table_valeur filter and DATA iterator, which accept and process serialized PHP data. An attacker with the ability to inject malicious serialized content (requiring prior access or an accompanying vulnerability) can trigger arbitrary object instantiation and potentially achieve remote code execution.

MitigationUpgrade SPIP to version 4.4.9 or later, which removes the deprecated serialized data handling in these components. The SPIP security screen does not mitigate this issue, so immediate patching is essential.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SpipApplication
Affected:>= 4.4.0, < 4.4.9

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed SPIP version
    Locate the version file or admin interface that displays the current SPIP version number
    Affected if The installed version is 4.4.0 through 4.4.8 (any version >= 4.4.0 but less than 4.4.9)
  2. Check for table_valeur filter usage in templates
    Search template files (.html files in the squelettes or themes folders) for occurrences of the #table_valeur filter or its equivalent syntax
    Affected if Templates in the public area use the table_valeur filter to process data
  3. Check for DATA iterator usage in templates or code
    Search template files and PHP code for #DATA or iterator usage with DATA, particularly in public-facing templates
    Affected if Templates in the public area use the DATA iterator to process serialized data
  4. Verify public area accessibility
    Confirm that the SPIP public-facing site is accessible and that the vulnerable filters/iterators can be invoked via URL parameters
    Affected if The public area is accessible and accepts parameters that could be processed by table_valeur or DATA iterator

You are affected if your installed SPIP version is 4.4.0 through 4.4.8 AND your public templates use the table_valeur filter or DATA iterator to handle data that could contain serialized content.

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
Upgrade available Upgrade to 4.4.9 or later
Fixed in 4.4.9
Interim mitigation

Upgrade SPIP to version 4.4.9 or later, which removes the deprecated serialized data handling in these components. The SPIP security screen does not mitigate this issue, so immediate patching is essential.

Recommended fix High confidence

SPIP 4.4.9

  1. 1. Backup your SPIP installation and database before proceeding with any upgrade.
  2. 2. Download SPIP version 4.4.9 or later from the official SPIP repository (git.spip.net or spip.net).
  3. 3. Replace the existing SPIP files with the new version, preserving your local configuration and customizations.
  4. 4. Run the upgrade process by accessing your site administrator area to apply database migrations.
  5. 5. Verify that the table_valeur filter and DATA iterator no longer accept serialized data in the public area.
  6. 6. After upgrading, review any custom code that uses serialized data with these components as the functionality has been deprecated.
Caveat The serialized data functionality in table_valeur filter and DATA iterator is deprecated and will be removed in SPIP 5; custom code relying on this feature may need adjustment

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

Fix this in Spip Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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