dbcve.org
SpipApplication

CVE-2026-26345

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-19
Fix available
A fix is available. Upgrade to 4.4.8 or later.
See remediation →
58/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
SPIP before 4.4.8 contains a stored cross-site scripting (XSS) vulnerability in the public area triggered in certain edge-case usage patterns. The echapper_html_suspect() function does not adequately sanitize user-controlled content, allowing authenticated users with content-editing privileges (e.g., author-level roles and above) to inject malicious scripts. The injected payload may be rendered across multiple pages within the framework and execute in the browser context of other users, including administrators. Successful exploitation can allow attackers to perform actions in the security context of the victim user, including unauthorized modification of application state. 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 has a stored XSS vulnerability in the public area. The echapper_html_suspect() function fails to properly sanitize user-controlled content, allowing authenticated users with author-level or higher privileges to inject malicious JavaScript. This payload persists in the database and executes in the browsers of other users viewing the content, including administrators.

MitigationUpgrade SPIP to version 4.4.8 or later to obtain the patched echapper_html_suspect() function. Review and test custom templates or plugins that may handle user-submitted HTML content.

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

CVSS:3.1/AV:N/AC:L/PR:L/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
    Locate the version file in your SPIP installation (commonly ecrire/inc_version.php or check the database configuration table spip_meta for 'version_installee'). Compare the version number to the affected range: >= 4.4.0 and < 4.4.8.
    Affected if The installed version falls within 4.4.0 through 4.4.7 inclusive.
  2. Confirm public area is accessible
    Verify that the public-facing section of your SPIP site is active and accessible to at least some users. The vulnerability exists in the public area rendering of user-submitted content.
    Affected if The public area is enabled and accessible without requiring authentication for viewing.
  3. Verify author-level or higher accounts exist
    Check the spip_auteurs database table for accounts with statut (status) indicating author-level or higher privileges (such as '0minirezo', '1comite', or similar privilege levels depending on your SPIP version).
    Affected if There exists at least one account with author-level (0minirezo) or higher privileges in the system.
  4. Inspect echapper_html_suspect function behavior
    Locate the echapper_html_suspect function in your SPIP source code (typically in ecrire/inc/texte_html.php or similar). Examine whether it properly escapes HTML entities in user-submitted content before rendering.
    Affected if The function does not properly sanitize or escape HTML special characters in user-controlled content before output.
  5. Review custom templates handling user HTML
    Examine any custom templates (in squelettes/ or themes/) or plugins that process or display user-submitted HTML content in the public area. Look for instances where echapper_html_suspect or similar sanitization functions are called.
    Affected if Custom templates or plugins handle user-submitted HTML content without proper sanitization before storage or display.

You are affected if your SPIP installation version is between 4.4.0 and 4.4.7 inclusive, the public area is accessible, and at least one author-level or higher account exists in the system.

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 obtain the patched echapper_html_suspect() function. Review and test custom templates or plugins that may handle user-submitted HTML content.

Recommended fix High confidence

SPIP 4.4.8

  1. Backup the current SPIP installation and database before proceeding with any changes
  2. Download SPIP version 4.4.8 from the official SPIP repository (git.spip.net or spip.net)
  3. Replace the existing SPIP files with the new version 4.4.8 files, preserving local configuration and custom files if necessary
  4. Run any available database migration scripts included in the 4.4.8 release
  5. Verify the upgrade was successful by logging into the admin area and checking the SPIP version display
  6. Clear any application caches to ensure the patched code is active

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

Fix this in Spip Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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