dbcve.org
SpipApplication

CVE-2026-27474

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-19
Fix available
A fix is available. Upgrade to 4.4.9 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.9 allows Cross-Site Scripting (XSS) in the private area, complementing an incomplete fix from SPIP 4.4.8. The echappe_anti_xss() function was not systematically applied to input, form, button, and anchor (a) HTML tags, allowing an attacker to inject malicious scripts through these elements. 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 · moderate confidence

SPIP before version 4.4.9 contains a stored Cross-Site Scripting (XSS) vulnerability in the private area. The echappe_anti_xss() sanitization function was not consistently applied to input, form, button, and anchor HTML tags, allowing attackers to inject malicious JavaScript through these elements. The SPIP security screen does not mitigate this issue.

MitigationUpgrade to SPIP 4.4.9 or later, which applies echappe_anti_xss() systematically to all vulnerable HTML tag types. Review user-submitted content in the private area for any existing malicious script injections.

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
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. Determine SPIP version
    Access the private area login page or check the includes/spip_version.php file to identify the installed SPIP version number
    Affected if The version is 4.4.0 through 4.4.8 inclusive (versions 4.4.x below 4.4.9)
  2. Confirm private area access
    Verify that the private area (administration interface) is enabled and accessible on the SPIP installation
    Affected if The private area is enabled and users can submit content through forms in that area
  3. Review echappe_anti_xss function
    Inspect the inc/filtres_echapper/php or similar sanitization files to verify if echappe_anti_xss() is applied to input, form, button, and anchor tags in the code
    Affected if The function is missing or inconsistently applied to those four HTML tag types
  4. Audit user-submitted content
    Examine the database tables containing content submitted through the private area (articles, forum posts, etc.) for any suspicious script tags or event handlers in HTML elements
    Affected if Malicious JavaScript code is found embedded in input, form, button, or anchor elements within private area content

The environment is affected if SPIP version 4.4.0 through 4.4.8 is running, the private area is accessible, and the echappe_anti_xss() function does not cover all four vulnerable HTML tag types.

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 to SPIP 4.4.9 or later, which applies echappe_anti_xss() systematically to all vulnerable HTML tag types. Review user-submitted content in the private area for any existing malicious script injections.

Recommended fix High confidence

SPIP 4.4.9

  1. 1. Back up your existing SPIP installation including the database and all files
  2. 2. Download SPIP 4.4.9 from the official SPIP website (https://www.spip.net/)
  3. 3. Extract the new version files
  4. 4. Replace the core files on your server with the new version, preserving your local/config/ directory and any custom plugins
  5. 5. Run any database migration scripts if prompted during the upgrade process
  6. 6. Clear the SPIP cache by deleting the tmp/cache/ directory contents
  7. 7. Verify the installation by logging into the private area
  8. 8. Test that the XSS fix is working by checking that the echappe_anti_xss() function properly escapes input, form, button, and anchor tags
Caveat Patch release with minimal expected breaking changes; preserve your config and plugins

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

Fix this in Spip Scoped from the published advisory
  • Consultation1.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,220
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,952.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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