How severe is CVE-2018-13982?

CVE-2018-13982 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-13982?

CVE-2018-13982 affects the following packages: smarty/smarty (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2018-13982?

Update smarty/smarty to 3.1.33 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-13982 is resolved across your whole dependency graph.

How do I detect CVE-2018-13982 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for smarty/smarty, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-13982 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2018-13982 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2018-13982, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-13982?

CVE-2018-13982 has an EPSS (Exploit Prediction Scoring System) score of 3.5%, placing it in the 89th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2018-13982?

CVE-2018-13982 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2018-13982 published, and has it been updated?

CVE-2018-13982 was published on September 18, 2018 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

CVE-2018-13982 — smarty

HIGHFix: smarty-php/smarty@2e081a5

CVE-2018-13982 is a high-severity (CVSS 7.5) Path Traversal vulnerability in smarty/smarty. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for smarty/smarty — see the affected versions and patch details below.

Smarty Path Traversal Vulnerability

Also known asGHSA-7gfx-wxfh-7rvm

Published

Sep 18, 2018

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs89th percentile — riskier than 89% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘smarty/smarty

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Smarty_Security::isTrustedResourceDir() in Smarty before 3.1.33 is prone to a path traversal vulnerability due to insufficient template code sanitization. This allows attackers controlling the executed template code to bypass the trusted directory security restriction and read arbitrary files.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`smarty/smarty`	all versions	3.1.33`composer require smarty/smarty:^3.1.33`

Affected Products

2 products · 2 configurations

debian linuxdebian

1 version

9.0

Application

smartysmarty

< 3.1.33

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Smarty_Security::isTrustedResourceDir() in Smarty before 3.1.33 is prone…

github.comNVDApr 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for smarty/smarty, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update smarty/smarty to 3.1.33 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-13982 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

UbuntuHIGH

USN-5348-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-13982 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works