PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-66738 SPIP CVE debrief

A code injection vulnerability exists in SPIP before version 4.4.18 when using SQLite-backed installations. An authenticated attacker with editor privileges can submit a crafted GET request to execute arbitrary OS commands. This vulnerability requires immediate attention from SPIP administrators, particularly those using SQLite-backed installations and granting editor privileges to users. The vulnerability allows authenticated attackers to execute arbitrary OS commands, potentially leading to system compromise and data breaches.

Vendor
SPIP
Product
Unknown
CVSS
HIGH 7.7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-10
Original CVE updated
2026-09-09
Advisory published
2026-08-10
Advisory updated
2026-09-09

Who should care

SPIP administrators and users with editor privileges, especially those using SQLite-backed installations, should be aware of this vulnerability and take immediate action to mitigate it. This includes upgrading SPIP to version 4.4.18 or later, restricting access to the navigation menu endpoint, and monitoring for suspicious activity on the web server.

Why it matters

This vulnerability requires immediate attention from SPIP administrators, particularly those using SQLite-backed installations and granting editor privileges to users. The vulnerability allows authenticated attackers to execute arbitrary OS commands, potentially leading to system compromise and data breaches.

  • Potential for arbitrary OS command execution
  • Elevation of privileges for authenticated attackers
  • Possible disruption of web server operations

Technical summary

The navigation menu endpoint in SPIP before 4.4.18 does not properly handle array-typed user input, allowing an authenticated attacker with editor privileges to inject arbitrary OS commands. This vulnerability affects SQLite-backed installations, while MySQL-backed installations are not affected. The vulnerability requires immediate attention from SPIP administrators, particularly those using SQLite-backed installations and granting editor privileges to users. The official CVE Program record and NIST NVD vulnerability detail provide additional context.

Defensive priority

High priority for systems using SPIP with SQLite, especially those with editor-level access.

Recommended defensive actions

  • Upgrade SPIP to version 4.4.18 or later
  • Restrict access to the navigation menu endpoint
  • Monitor for suspicious activity on the web server
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is confirmed in SPIP versions before 4.4.18 with SQLite installations. MySQL-backed installations are not affected. Editor privileges are required for exploitation. The CVE record was published on 2026-08-10T16:19:48.607Z and has not been modified since then. The official CVE Program record and NIST NVD vulnerability detail provide additional context.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-66738 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-66738

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-66738 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-66738

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.