# CVE-2026-27744: SPIP tickets < 4.3.3 Unauthenticated RCE

> Unauthenticated attackers can execute arbitrary code on the web server via crafted input in the SPIP tickets plugin forum preview.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Feb 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-68cf-j259-wgr8

## What is CVE-2026-27744?

CVE-2026-27744 is a critical code injection vulnerability in SPIP tickets, published on 25 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-27744?

It affects 1 product.


Products: Spip Tickets.

## How do I fix CVE-2026-27744?

No fix has been published for CVE-2026-27744 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-27744 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27744 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-27744 and fix it if it is affected.

What it is: CVE-2026-27744 is a critical code injection vulnerability in SPIP tickets, published on 25 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27744 exists.

Affected product: SPIP tickets. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-27744/ (Markdown: https://insights.sbomify.com/CVE-2026-27744/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27744
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27744
- OSV: https://osv.dev/vulnerability/CVE-2026-27744

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-27744/
Summaries are generated and may contain mistakes; the official description above is the record.