# CVE-2026-27474: SPIP < 4.4.9 Cross-Site Scripting in Private Area (Incomplete Fix)

> Attackers can inject malicious scripts into SPIP private area elements due to incomplete XSS filtering, potentially compromising user sessions.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Feb 2026
- **Updated:** 5 Mar 2026
- **Also known as:** DEBIAN-CVE-2026-27474, GHSA-c33v-v6jp-566m, UBUNTU-CVE-2026-27474

## What is CVE-2026-27474?

CVE-2026-27474 is a medium-severity cross-site scripting vulnerability in Spip Spip, published on 19 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

SPIP before 4.4.9 allows Cross-Site Scripting (XSS) in the private area, complementing an incomplete fix from SPIP 4.4.8. The echappe_anti_xss() function was not systematically applied to input, form, button, and anchor (a) HTML tags, allowing an attacker to inject malicious scripts through these elements. This vulnerability is not mitigated by the SPIP security screen.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Spip Spip.

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

Upgrade to a fixed version.

## Is CVE-2026-27474 being exploited?

There is no known exploitation of CVE-2026-27474 in the wild and no public exploit code.

## Other vulnerabilities in Spip Spip

- [CVE-2012-4331](https://insights.sbomify.com/CVE-2012-4331/): Other in n/a (critical 10.0)
- [CVE-2008-5812](https://insights.sbomify.com/CVE-2008-5812/): Other in n/a (critical 10.0)
- [CVE-2024-8517](https://insights.sbomify.com/CVE-2024-8517/): SPIP Bigup Multipart File Upload OS Command Injection (critical 9.8)
- [CVE-2023-24258](https://insights.sbomify.com/CVE-2023-24258/): SQL injection in n/a (critical 9.8)
- [CVE-2017-9736](https://insights.sbomify.com/CVE-2017-9736/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27474 is a medium-severity cross-site scripting vulnerability in Spip Spip, published on 19 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-27474 in the wild and no public exploit code.

Affected product: Spip Spip. 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-27474/ (Markdown: https://insights.sbomify.com/CVE-2026-27474/index.md)
```

## Sources

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

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