# Smarty Path Traversal Vulnerability

Advisory record · `GHSA-65j5-vpm7-6xp4`

- **Identifiers:** `GHSA-65j5-vpm7-6xp4` · `CVE-2018-16831` · `PKSA-thph-wfk6-pp4j`
- **State:** Confirmed
- **Severity:** CVSS 5.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 14 May 2022
- **Updated:** 16 Feb 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 May 2022, 01:58 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `smarty/smarty` (Packagist): affected `<3.1.33`; fixed in `3.1.33`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.9 Medium, CVSS 3.0: `CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.027, the 86th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 14 May 2022. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-65j5-vpm7-6xp4](https://github.com/advisories/GHSA-65j5-vpm7-6xp4)
- [OSV: GHSA-65j5-vpm7-6xp4](https://osv.dev/vulnerability/GHSA-65j5-vpm7-6xp4)
- <https://nvd.nist.gov/vuln/detail/CVE-2018-16831>
- <https://github.com/smarty-php/smarty/issues/486>
- <https://github.com/smarty-php/smarty/commit/f9ca3c63d1250bb56b2bda609dcc9dd81f0065f8>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/smarty/smarty/CVE-2018-16831.yaml>
- <https://github.com/smarty-php/smarty>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-65j5-vpm7-6xp4>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-65j5-vpm7-6xp4/>. Everything for agents: <https://agentprime.io/llms.txt>.
