dbcve.org
TicketsApplication · Spip

CVE-2026-27744

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-25
Fix available
A fix is available. Upgrade to 4.3.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
The SPIP tickets plugin versions prior to 4.3.3 contain an unauthenticated remote code execution vulnerability in the forum preview handling for public ticket pages. The plugin appends untrusted request parameters into HTML that is later rendered by a template using unfiltered environment rendering (#ENV**), which disables SPIP output filtering. As a result, an unauthenticated attacker can inject crafted content that is evaluated through SPIP's template processing chain, leading to execution of code in the context of the web 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 confidence

The SPIP tickets plugin versions before 4.3.3 have an unauthenticated RCE vulnerability in the forum preview handling for public ticket pages. The plugin appends untrusted request parameters directly into HTML rendered by a template using unfiltered environment rendering (#ENV**), which disables SPIP's output filtering. This allows unauthenticated attackers to inject malicious content through SPIP's template processing chain, achieving code execution in the web server context.

MitigationUpgrade the SPIP tickets plugin to version 4.3.3 or later to obtain the patched version with proper output filtering.

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
TicketsApplication
Affected:< 4.3.3

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

CVSS:3.1/AV:N/AC:L/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 tickets plugin installation and version
    Access the SPIP administration panel, navigate to the plugin management section, and locate the tickets plugin to view its installed version number. Alternatively, check the plugin's main PHP file or manifest.xml for the version declaration.
    Affected if The tickets plugin is installed and its version number is below 4.3.3
  2. Verify public ticket pages are accessible
    Confirm that the tickets plugin's public-facing pages are enabled and reachable. This typically involves checking the plugin configuration in SPIP or attempting to access a public ticket URL.
    Affected if Public ticket pages are accessible without authentication, enabling the attack surface for the forum preview vulnerability
  3. Confirm forum preview functionality is active
    Check whether the forum preview feature is enabled within the tickets plugin settings or SPIP's forum configuration. The vulnerability exists in the forum preview handling for public ticket pages.
    Affected if The forum preview feature is enabled on public ticket pages, allowing untrusted input to be processed through the vulnerable template rendering path

You are affected if the SPIP tickets plugin is installed with a version lower than 4.3.3 and public ticket pages with forum preview functionality are accessible.

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
Upgrade available Upgrade to 4.3.3 or later
Fixed in 4.3.3
Vendor patch git.spip.net →
Interim mitigation

Upgrade the SPIP tickets plugin to version 4.3.3 or later to obtain the patched version with proper output filtering.

Recommended fix High confidence

Tickets plugin version 4.3.3

  1. 1. Identify the SPIP installation and locate the tickets plugin directory (typically in plugins/ or extensions/)
  2. 2. Backup the current tickets plugin directory and database before making changes
  3. 3. Download the fixed tickets plugin version 4.3.3 from the official SPIP plugins repository at plugins.spip.net or git.spip.net
  4. 4. Replace the existing tickets plugin folder with the new version 4.3.3
  5. 5. Clear any SPIP caches via the private area (Maintenance > Clear cache) or by deleting tmp/cache/ directory
  6. 6. Verify the upgrade was successful by checking the plugin version in the SPIP administration panel
  7. 7. Test that the tickets functionality works correctly and that the vulnerability is no longer exploitable
Caveat Review plugin changelog for any breaking changes between your current version and 4.3.3; test in staging environment first if possible

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

Fix this in Tickets Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27744 — 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-27744 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