CVE-2009-5054
Smarty Does Not Consider Umask Values When Setting Permissions
Smarty before 3.0.0 beta 4 does not consider the umask value when setting the permissions of files, which might allow attackers to bypass intended access restrictions via standard filesystem operations.
Exploit likelihood
What each source reports
NVD Score used
Smarty before 3.0.0 beta 4 does not consider the umask value when setting the permissions of files, which might allow attackers to bypass intended access restrictions via standard filesystem operations.
- Record
CVE-2009-5054- CVSS 2.0
- 7.5 High
AV:N/AC:L/Au:N/C:P/I:P/A:P - Weakness
- CWE-264
- Updated
- 2026-11-02
CVE List No score
Smarty before 3.0.0 beta 4 does not consider the umask value when setting the permissions of files, which might allow attackers to bypass intended access restrictions via standard filesystem operations.
- Record
CVE-2009-5054- Updated
- 2026-11-02
EUVDEUVD-2022-2823 No score
Smarty before 3.0.0 beta 4 does not consider the umask value when setting the permissions of files, which might allow attackers to bypass intended access restrictions via standard filesystem operations.
- Record
EUVD-2022-2823- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-6m9f-8vwq-97pm No score
Smarty Does Not Consider Umask Values When Setting Permissions
Smarty before 3.0.0 beta 4 does not consider the umask value when setting the permissions of files, which might allow attackers to bypass intended access restrictions via standard filesystem operations.
- Record
GHSA-6m9f-8vwq-97pm- Weakness
- CWE-281
- Updated
- 2026-11-02
OSV No score
Smarty before 3.0.0 beta 4 does not consider the umask value when setting the permissions of files, which might allow attackers to bypass intended access restrictions via standard filesystem operations.
- Record
CVE-2009-5054- Updated
- 2026-11-02
OSVDEBIAN-CVE-2009-5054 No score
Smarty before 3.0.0 beta 4 does not consider the umask value when setting the permissions of files, which might allow attackers to bypass intended access restrictions via standard filesystem operations.
- Record
DEBIAN-CVE-2009-5054- Updated
- 2026-11-02
OSVGHSA-6m9f-8vwq-97pm No score
Smarty Does Not Consider Umask Values When Setting Permissions
Smarty before 3.0.0 beta 4 does not consider the umask value when setting the permissions of files, which might allow attackers to bypass intended access restrictions via standard filesystem operations.
- Record
GHSA-6m9f-8vwq-97pm- Weakness
- CWE-281
- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
smarty/smartyPackagist |
before 3.0.0-beta4 | 3.0.0-beta4 |
smarty3Debian:12 |
before 3.0~rc1-1 | 3.0~rc1-1 |
smarty3Debian:13 |
before 3.0~rc1-1 | 3.0~rc1-1 |
smarty3Debian:14 |
before 3.0~rc1-1 | 3.0~rc1-1 |
smarty/smartyPackagist |
before 3.0.0-beta4, plus listed versions v2.6.24v2.6.25v2.6.26v2.6.27v2.6.28 Show 4 moreShow lessv2.6.29v2.6.30v2.6.31v2.6.33 |
3.0.0-beta4 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2009-5054 is a high vulnerability (CVSS 7.5) in Smarty, published February 3, 2011. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.59%, the 75th percentile. Fixed in smarty/smarty 3.0.0-beta4.
References
smarty-php.googlecode.com/svn/trunk/distribution/change_log.txt
nvd.nist.gov/vuln/detail/CVE-2009-5054
web.archive.org/web/20101116174040/http://smarty-php.googlecode.com/svn/trunk/distribution/change_log.txt
github.com/advisories/GHSA-6m9f-8vwq-97pm
security-tracker.debian.org/tracker/CVE-2009-5054