CVE-2026-22206
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 · uneditedSPIP versions prior to 4.4.10 contain a SQL injection vulnerability that allows authenticated low-privilege users to execute arbitrary SQL queries by manipulating union-based injection techniques. Attackers can exploit this SQL injection flaw combined with PHP tag processing to achieve remote code execution on the server.
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 · high confidenceSPIP versions before 4.4.10 contain a SQL injection vulnerability in a component accessible to authenticated low-privilege users. Attackers can exploit this via union-based SQL injection to extract or modify database content. The vulnerability can be chained with SPIP's PHP tag processing functionality to achieve remote code execution on the affected server.
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< 4.4.10CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed SPIP versionAccess the SPIP administration panel and navigate to the configuration or about page to view the version number. Alternatively, check the version.php file in the SPIP installation directory if accessible.Affected if The installed version is any version of SPIP before 4.4.10
-
Verify user authentication statusDetermine whether there are any authenticated users in the SPIP system, particularly low-privilege users such as registered visitors or authors with minimal permissions.Affected if Any authenticated low-privilege user account exists in the SPIP installation
-
Check PHP tag processing configurationInspect the SPIP configuration files (typically ecrire/inc_version.php or configuration settings in the admin panel) to determine if PHP tag processing is enabled or if the ability to process PHP tags is available to users.Affected if PHP tag processing functionality is enabled and accessible to authenticated users, which would allow chaining with the SQL injection for remote code execution
You are affected if your SPIP installation version is before 4.4.10 and you have any authenticated users, especially when PHP tag processing is enabled, as this would allow both data extraction via SQL injection and potential remote code execution.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.4.10
Upgrade SPIP to version 4.4.10 or later to remediate this vulnerability. If immediate patching is not possible, restrict access to the affected administrative endpoints to trusted users only.
SPIP 4.4.10
- Create a full backup of the SPIP database and all files before proceeding
- Download SPIP version 4.4.10 from the official repository (git.spip.net or spip.net)
- Follow the official SPIP upgrade procedure to replace core files while preserving the/IMG and/local directories
- After upgrade, verify the version number in the administration interface shows 4.4.10
- Test critical functionality (login, article editing, form submissions) to ensure the upgrade was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22206 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22206 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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