dbcve.org
SpipApplication

CVE-2025-71240

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-19
Fix available
A fix is available. Upgrade to 4.2.15 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.2.15 allows Cross-Site Scripting (XSS) via crafted content in HTML code tags. The application does not properly verify JavaScript within code tags, allowing an attacker to inject malicious scripts that execute in a victim's browser.

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 4.2.15 is vulnerable to stored Cross-Site Scripting (XSS) due to insufficient validation of JavaScript within HTML code tags. Attackers can inject malicious scripts that execute in victims' browsers when viewing crafted content.

MitigationUpgrade to SPIP version 4.2.15 or later which includes proper sanitization of JavaScript within code tags. Additionally, implement Content Security Policy (CSP) headers as a defense-in-depth measure.

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.2.0, < 4.2.15

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. Confirm SPIP installation
    Locate the SPIP installation by searching for the main entry point (spip.php) or the core includes directory (inc/) in your web root. Common paths include /spip/ or the document root.
    Affected if SPIP is found in the environment
  2. Identify installed SPIP version
    Access the SPIP administration panel and navigate to Configuration > Informations or check the version file (inc/version.php) in the SPIP installation directory. The version number is typically displayed clearly.
    Affected if Version is 4.2.0 through 4.2.14 (any version >= 4.2.0 and < 4.2.15)
  3. Verify version is within affected range
    Compare your identified version number against the vulnerable range: versions 4.2.0, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.2.5, 4.2.6, 4.2.7, 4.2.8, 4.2.9, 4.2.10, 4.2.11, 4.2.12, 4.2.13, or 4.2.14.
    Affected if Your installed version matches any version from 4.2.0 up to but not including 4.2.15
  4. Check for HTML code tag usage
    Review content creation areas in SPIP (articles, rubriques, or any content types that accept HTML or code blocks) to determine if users can insert HTML code tags containing JavaScript. This feature is typically available in the text editor when HTML is permitted.
    Affected if The platform allows users to create or edit content with HTML code tags that can contain JavaScript

You are affected if SPIP version 4.2.0 through 4.2.14 is installed and your content editing functionality permits HTML code tags with JavaScript 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.2.15 or later
Fixed in 4.2.15
Interim mitigation

Upgrade to SPIP version 4.2.15 or later which includes proper sanitization of JavaScript within code tags. Additionally, implement Content Security Policy (CSP) headers as a defense-in-depth measure.

Recommended fix High confidence

SPIP 4.2.15

  1. 1. Create a complete backup of the SPIP database and all web files
  2. 2. Download SPIP 4.2.15 from the official SPIP repository (git.spip.net or spip.net)
  3. 3. Replace the existing SPIP core files with the new version 4.2.15 files
  4. 4. Run the SPIP upgrade/migration process if prompted (typically via the private area)
  5. 5. Verify the installation by logging into the private area
  6. 6. Test that HTML code tags now properly sanitize embedded JavaScript content
  7. 7. Clear any caching systems if enabled
Caveat Minor - this is a security patch release; standard SPIP upgrade precautions apply (backup before upgrading)

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

Fix this in Spip Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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