dbcve.org
SpipApplication

CVE-2025-71241

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-19
Fix available
A fix is available. Upgrade to 4.1.20 / 4.2.17 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.3.6, 4.2.17, and 4.1.20 allows Cross-Site Scripting (XSS) in the private area. The content of the error message displayed by the 'transmettre' API is not properly sanitized, allowing an attacker to inject malicious scripts. This vulnerability is 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 CMS before versions 4.3.6, 4.2.17, and 4.1.20 contains a stored Cross-Site Scripting (XSS) vulnerability in the private area. The 'transmettre' API fails to properly sanitize error message content before display, allowing authenticated attackers to inject malicious JavaScript through crafted input. The SPIP security screen provides partial mitigation but the underlying input validation failure must be addressed.

MitigationUpgrade SPIP to version 4.3.6, 4.2.17, or 4.1.20 or later to receive the vendor patch. The SPIP security screen provides some defense-in-depth but should not be relied upon as the sole mitigation.

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.1.0, < 4.1.20>= 4.2.0, < 4.2.17>= 4.3.0, < 4.3.6

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
    Locate the version file in your SPIP installation (typically includes/version.php or similar) and read the defined SPIP_VERSION constant. Alternatively, check the footer of any private area page where the version number is often displayed.
    Affected if The installed version falls within any of these ranges: 4.1.0 to 4.1.19, 4.2.0 to 4.2.16, or 4.3.0 to 4.3.5.
  2. Confirm access to the private area
    Verify that user accounts exist with access to the SPIP private area (the espace prive). This vulnerability requires an authenticated attacker to exploit the 'transmettre' API endpoint.
    Affected if Authenticated users have access to the private area and can interact with the 'transmettre' API functionality.
  3. Check if SPIP security screen is enabled
    Review your SPIP configuration (config/mes_options.php or similar) for the 'security_screen' configuration option. This feature provides partial mitigation but should not be relied upon as the sole defense.
    Affected if The SPIP security screen is disabled or not properly configured, providing no defense-in-depth layer.

You are affected if your SPIP installation version is 4.1.x below 4.1.20, 4.2.x below 4.2.17, or 4.3.x below 4.3.6, and authenticated users can access the private area with the 'transmettre' API.

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.1.20 / 4.2.17 / 4.3.6 or later
Fixed in 4.1.204.2.174.3.6
Interim mitigation

Upgrade SPIP to version 4.3.6, 4.2.17, or 4.1.20 or later to receive the vendor patch. The SPIP security screen provides some defense-in-depth but should not be relied upon as the sole mitigation.

Recommended fix High confidence

SPIP 4.3.6 (or 4.2.17 / 4.1.20 depending on your current branch)

  1. Download SPIP version 4.3.6 (or 4.2.17 for the 4.2.x branch, or 4.1.20 for the 4.1.x branch) from the official SPIP repository
  2. Back up your existing SPIP installation and database
  3. Replace the existing SPIP files with the new version files
  4. Verify the upgrade was successful by logging into the private area
  5. Test that the 'transmettre' API now properly sanitizes error message content

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-2025-71241 — 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-71241 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