Skip to content
Fencer Intel
high 7.5

CVE-2009-5054 json

Smarty Does Not Consider Umask Values When Setting Permissions

published 15y ago modified 4mo ago also GHSA-6m9f-8vwq-97pm , EUVD-2022-2823

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.6%
EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits
0
none known

Summary

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.

Patch / fix

  • packagist smarty/smarty 3.0.0-beta4
  • smarty3 Debian 14, Debian 13, Debian 12 3.0~rc1-1

debian advisories DEBIAN-CVE-2009-5054

Is CVE-2009-5054 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2009-5054 updated cvss 4.3

php-Smarty: Does not consider the umask value when setting the permissions of files

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.59% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected packages

ecosystem package affected fixed in
packagist smarty/smarty
<3.0.0-beta4
3.0.0-beta4

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
  • CWE-281 Improper Preservation of Permissions

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.