Quick answers
- Is CVE-2026-66738 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-66738 being exploited in the wild.
- How severe is CVE-2026-66738?
- High severity, with a CVSS score of 8.8, published 10 August 2026.
- Which products and versions are affected?
- Spip before 4.4.18.
- Is there a fix for CVE-2026-66738?
- A patch was published on 2026-08-10: SPIP 4.4.18 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-66738 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-66738?
- 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.
Technical details
A code injection vulnerability exists in SPIP's navigation menu endpoint (/ecrire/?exec=navigation) where improper handling of array-typed user input bypasses input sanitization and allows an attacker to break out of an internal quoted string context during PHP evaluation. The vulnerability requires authentication (minimum editor/redacteur privileges) and is triggered via a single crafted GET request. An authenticated attacker can achieve arbitrary OS command execution in the web server process context. The vulnerability affects only SQLite-backed installations; MySQL-backed deployments are not affected. The fix is available in SPIP 4.4.18 and later versions.
Affected products
- SPIP SPIP before 4.4.18
Timeline
- 2026-08-10: disclosed
- 2026-08-10: patched: SPIP 4.4.18 released