CVE-2026-122032
Deferred Deferred - Pending Action

SPIP SQL Injection via Parameter Mismatch

Publication date: 2026-11-04

Last updated on: 2026-11-04

Assigner: VulnCheck

Description
SPIP before 4.4.29 contains a SQL injection vulnerability that allows authenticated attackers with back-office access to inject arbitrary SQL by submitting a differing where parameter value in the POST body versus the GET query string on the /ecrire/?exec=articles endpoint, bypassing spip_sanitize_from_request() sanitization. Attackers can exploit this request parameter mismatch to extract database contents, including protected articles and bcrypt password hashes of users.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-04
Last Modified
2026-11-04
Generated
2026-11-04
AI Q&A
2026-11-04
EPSS Evaluated
N/A
NVD
CVE-2026-122032
EUVD
EUVD-2026-116939

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
SPIP SPIP 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is an authenticated SQL injection vulnerability in SPIP versions before 4.4.29. Attackers with back-office access can exploit a mismatch between the 'where' parameter in POST body and GET query string on the /ecrire/?exec=articles endpoint to bypass sanitization and inject arbitrary SQL commands. This allows extraction of sensitive database contents, including protected articles and bcrypt password hashes.

Detection Guidance

To detect this vulnerability, check if your SPIP instance is running a version before 4.4.29. Inspect HTTP requests to /ecrire/?exec=articles for mismatched 'where' parameters in POST body and GET query string. Look for unusual SQL query patterns or database access logs indicating unauthorized extraction attempts.

Impact Analysis

An attacker could steal sensitive data like protected articles or user password hashes, potentially leading to unauthorized access, data breaches, or further attacks. Systems running vulnerable SPIP versions are at risk if attackers gain back-office access.

Compliance Impact

This vulnerability could lead to unauthorized data access or breaches, violating GDPR's data protection requirements and HIPAA's safeguards for protected health information. Organizations may face compliance penalties, legal liabilities, and reputational damage if exploited.

Mitigation Strategies

Immediately update SPIP to version 4.4.29 or later. Ensure the plugin memoization is updated to version 4.1.2 before applying the SPIP update. Monitor for suspicious database queries or unauthorized access attempts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-122032. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...