Is CVE-2026-122032 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-122032 being exploited in the wild.

How severe is CVE-2026-122032?

Medium severity, with a CVSS score of 6.5, published 4 November 2026.

Is there a fix for CVE-2026-122032?

Yes: fixed in 4.4.29. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-122032 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-122032?

Check whether you run Spip at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-122032: SPIP SQL injection via parameter mismatch

CVE-2026-122032 · Severity: medium · CVSS 6.5 · Published 2026-11-04

SPIP is a web content management system used to build and manage websites. An authenticated attacker with back-office access can exploit a SQL injection vulnerability by submitting conflicting parameter values in the GET and POST requests, allowing them to extract sensitive database contents including protected articles and user password hashes. This vulnerability bypasses SPIP's standard input sanitization function.

Technologies: Spip. Vendors: Spip.

Quick answers

Is CVE-2026-122032 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-122032 being exploited in the wild.
How severe is CVE-2026-122032?: Medium severity, with a CVSS score of 6.5, published 4 November 2026.
Which products and versions are affected?: Spip before 4.4.29.
Is there a fix for CVE-2026-122032?: Yes: fixed in 4.4.29. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-122032 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-122032?: Check whether you run Spip at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 4.4.29

Technical details

A SQL injection vulnerability exists in SPIP's /ecrire/?exec=articles endpoint where the spip_sanitize_from_request() sanitization can be bypassed by submitting different values for the same parameter in the GET query string versus the POST body (specifically the "where" parameter). Authenticated back-office users can exploit this request parameter mismatch to execute arbitrary SQL queries and access database contents including protected articles and bcrypt password hashes. The vulnerability requires authentication and back-office access.

Affected products

SPIP SPIP before 4.4.29

Timeline

2026-11-04: disclosed
2026-11-04: patched: SPIP 4.4.29 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.