dbcve.org
SpipApplication

CVE-2025-71244

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-19
Fix available
A fix is available. Upgrade to 4.3.9 / 4.4.5 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.5 and 4.3.9 allows an Open Redirect via the login form when used in AJAX mode. An attacker can craft a malicious URL that, when visited by a victim, redirects them to an arbitrary external site after login. This vulnerability only affects sites where the login page has been overridden to function in AJAX mode. It 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 4.4.5 and 4.3.9 contains an open redirect vulnerability in the AJAX-mode login form. Attackers can craft malicious URLs containing a crafted redirect parameter that, after a victim successfully logs in, redirects them to an arbitrary external website. This only affects sites where the login page has been overridden to function in AJAX mode.

MitigationUpgrade to SPIP 4.4.5 or 4.3.9. As a temporary measure, disable AJAX mode on custom login forms or implement server-side validation of redirect parameters before use.

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.3.0, < 4.3.9>= 4.4.0, < 4.4.5

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 installed SPIP version
    Locate and read the version file (typically ecrire/inc_version.php) or check the version displayed in the SPIP admin footer
    Affected if The version is >= 4.3.0 and < 4.3.9, OR >= 4.4.0 and < 4.4.5
  2. Identify custom login form templates
    Search the sites templates and configuration for any custom login form implementations (typically in squelettes or themes directories)
    Affected if Custom login form templates exist in the installation
  3. Check for AJAX mode on login forms
    Inspect custom login form templates or configuration files for AJAX-related attributes or flags (such as AJAX-enabled form classes, #FORMULAIRE_LOGIN with AJAX wrappers, or explicit AJAX mode settings)
    Affected if AJAX mode is enabled on any custom login form (the vulnerability only applies when the login page has been overridden to function in AJAX mode)
  4. Inspect redirect parameter handling
    Examine the login form processing code to see how the redirect parameter is handled after successful authentication
    Affected if The redirect parameter is used without server-side validation before issuing a location header

The site is affected only if running a vulnerable SPIP version (4.3.0-4.3.8 or 4.4.0-4.4.4) AND has a custom login form operating in AJAX mode that accepts and uses a redirect parameter without validation.

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.3.9 / 4.4.5 or later
Fixed in 4.3.94.4.5
Interim mitigation

Upgrade to SPIP 4.4.5 or 4.3.9. As a temporary measure, disable AJAX mode on custom login forms or implement server-side validation of redirect parameters before use.

Recommended fix High confidence

SPIP 4.3.9 or 4.4.5 (depending on your current branch)

  1. Identify current SPIP version by checking the footer of any admin page or the inc/define.php file
  2. Determine which version branch you're on (4.3.x or 4.4.x)
  3. Backup the database and all files before upgrading
  4. Download the fixed version (4.3.9 for 4.3.x branch or 4.4.5 for 4.4.x branch) from https://www.spip.net/en_download
  5. Extract the archive and replace the existing SPIP files, preserving the config/ and IMG/ directories
  6. Run the upgrade by visiting the site URL to trigger any necessary database migrations
  7. Verify the login form works correctly after upgrade

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 / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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