dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-8430

HIGH · 8.1 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
SPIP versions prior to 4.4.14 contain a remote code execution vulnerability in the public space that is limited to certain nginx configurations, allowing attackers to execute arbitrary code in the context of the web server. Attackers can exploit this vulnerability through specific nginx configuration scenarios to achieve code execution, and this issue is not mitigated by the SPIP security screen.

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 · moderate confidence

SPIP versions before 4.4.14 contain an RCE vulnerability in the public space that is triggered only under specific nginx configurations, allowing attackers to execute arbitrary code as the web server user. This issue bypasses the SPIP security screen, making it exploitable even when standard protections are in place.

MitigationUpgrade SPIP to version 4.4.14 or later and audit nginx configuration to identify and remediate the specific configuration patterns that enable this RCE vector.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SPIP installation and version
    Locate the SPIP core file (ecrire/inc_version.php or ecrire/inc_version.php) and read its version definition, or check the site meta tag in HTML source for the version number
    Affected if The installed SPIP version is below 4.4.14 (e.g., 4.4.13, 4.4.12, earlier versions)
  2. Confirm web server is nginx
    Check server response headers for 'Server: nginx' or examine server configuration files for nginx directives
    Affected if nginx is the web server handling SPIP requests (the vulnerability requires specific nginx configurations)
  3. Check nginx configuration for alias or rewrite rules
    Review nginx site configuration files for any alias directives, rewrite rules, or location blocks that interact with SPIP's public area paths, especially those involving file uploads or cache directories
    Affected if nginx has configuration patterns that could enable path traversal or arbitrary file inclusion in the public area
  4. Verify public area accessibility
    Confirm the SPIP public area (root URL of the site) is reachable without authentication
    Affected if The public area is exposed and accessible (exploitation occurs through the unauthenticated public interface)

The environment is affected if SPIP version is below 4.4.14 AND nginx serves the SPIP public area with configurations that support the exploitation path.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SPIP to version 4.4.14 or later and audit nginx configuration to identify and remediate the specific configuration patterns that enable this RCE vector.

Recommended fix Moderate confidence

SPIP 4.4.14

  1. 1. Backup your current SPIP installation and database before proceeding with any upgrade.
  2. 2. Download SPIP version 4.4.14 from the official SPIP website (https://www.spip.net/).
  3. 3. Replace the existing SPIP files with the new version 4.4.14 files, preserving your local configuration and data files.
  4. 4. Verify the nginx configuration: ensure that php scripts are not being executed in directories where user uploads are stored, as this vulnerability is specific to certain nginx configurations that allow script execution in upload directories.
  5. 5. After upgrading, clear any caches and verify that the site functions correctly.
  6. 6. Review the SPIP security screen settings to ensure they are properly configured, though note this vulnerability is not mitigated by the security screen.
Caveat Point release upgrades typically do not include breaking changes; however, always test in a staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8430 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8430 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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