dbcve.org
SpipApplication

CVE-2026-26223

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-19
Fix available
A fix is available. Upgrade to 4.4.8 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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.8 allows cross-site scripting (XSS) in the private area via malicious iframe tags. The application does not properly sandbox or escape iframe content in the back-office, allowing an attacker to inject and execute malicious scripts. The fix adds a sandbox attribute to iframe tags in the private area. 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 version 4.4.8 contains a cross-site scripting (XSS) vulnerability in its private/back-office area. The application fails to properly sandbox or escape iframe tags, allowing attackers to inject malicious iframe content that can execute arbitrary scripts. The fix involves adding a sandbox attribute to iframe elements in the private area.

MitigationUpgrade SPIP to version 4.4.8 or later to receive the fix that adds the sandbox attribute to iframe tags. The SPIP security screen does not mitigate this vulnerability, so the upgrade is required.

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.8

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
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 installed SPIP version
    Check your SPIP installation's version number, typically found in the site footer of the public or private area, or in a version file within the installation directory
    Affected if The installed version is 4.4.0, 4.4.1, 4.4.2, 4.4.3, 4.4.4, 4.4.5, 4.4.6, or 4.4.7 (any version >= 4.4.0 but < 4.4.8)
  2. Confirm private back-office area is in use
    Log into the SPIP private area (typically at /ecrire/ or /private/ path) and verify the administrative interface is accessible and active
    Affected if The private back-office area is accessible and the SPIP version falls within the affected range
  3. Inspect iframe usage in private area templates
    Examine the SPIP templates or code that render iframe elements within the private area, looking for any code that outputs iframe tags
    Affected if Iframe elements are present in the private area templates and the version is in the affected range
  4. Check for sandbox attribute on iframe elements
    Review the iframe tag implementations in the private area code and verify whether a 'sandbox' attribute is defined on iframe elements
    Affected if Iframe elements in the private area lack a sandbox attribute or the sandbox attribute is not properly configured, and the version is in the affected range

You are affected if your SPIP installation is version 4.4.0 through 4.4.7 and the private back-office area contains iframe elements without a proper sandbox attribute.

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.8 or later
Fixed in 4.4.8
Interim mitigation

Upgrade SPIP to version 4.4.8 or later to receive the fix that adds the sandbox attribute to iframe tags. The SPIP security screen does not mitigate this vulnerability, so the upgrade is required.

Recommended fix High confidence

4.4.8

  1. Backup the current SPIP installation and database before upgrading
  2. Download SPIP version 4.4.8 from the official SPIP website (https://www.spip.net)
  3. Extract the new version archive
  4. Replace the existing SPIP files with the new version files, preserving the ./config and ./IMG directories
  5. Verify the upgrade was successful by logging into the private area (back-office)
  6. Confirm the sandbox attribute has been added to iframe tags by inspecting page source in the private area

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

Fix this in Spip Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

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