dbcve.org
SmartyApplication

CVE-2010-4723

HIGH · 9.3 CVSS v2.0 Published 2011-02-03
Fix available
A fix is available. Upgrade to after 3.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Smarty before 3.0.0, when security is enabled, does not prevent access to the (1) dynamic and (2) private object members of an assigned object, which has unspecified impact and remote attack vectors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Smarty before 3.0.0 has a security bypass vulnerability where, even with security mode enabled, the template engine fails to properly restrict access to dynamic and private object members of assigned objects. This allows remote attackers to potentially access restricted object properties through template variables.

MitigationUpgrade Smarty to version 3.0.0 or later where this security restriction is properly enforced. If immediate upgrade is not feasible, audit all template files for object assignments and ensure no sensitive objects are exposed to the template layer.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SmartyApplication
Affected:<= 3.0.0= 1.0= 1.0a= 1.0b= 1.1.0= 1.2.0= 1.2.1= 1.2.2= 1.3.0= 1.3.1= 1.3.2= 1.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Smarty version
    Check your project's Smarty library version by locating the Smarty.class.php or similar core file and reading the version constant or changelog. Common locations: vendor/smarty/smarty/ or lib/Smarty/.
    Affected if The version is 3.0.0 or lower, specifically 1.0, 1.0a, 1.0b, 1.1.0, 1.2.0, 1.2.1, 1.2.2, 1.3.0, 1.3.1, 1.3.2, or 1.4.0.
  2. Verify Smarty security mode configuration
    Search your Smarty initialization code for $smarty->security = true; or $smarty->setSecurityEnabled(true); to determine if security mode is enabled.
    Affected if Security mode is enabled, but the vulnerability still exists in these versions regardless of this setting.
  3. Identify object assignments in PHP code
    Search your application source code for patterns like $smarty->assign($object) or $tpl->assign('varname', $object) where $object is a class instance.
    Affected if Your application assigns PHP objects to Smarty templates.
  4. Inspect templates for object property access
    Review .tpl template files for syntax like {$obj->property} or {$obj->dynamicProperty} to see if assigned objects are accessed within templates.
    Affected if Templates access properties of assigned objects, especially dynamic or private members that should be restricted.

Your environment is affected if you run Smarty version 3.0.0 or any of the listed 1.x versions and your application assigns objects to templates that are then accessed within the template layer.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.0.0
Interim mitigation

Upgrade Smarty to version 3.0.0 or later where this security restriction is properly enforced. If immediate upgrade is not feasible, audit all template files for object assignments and ensure no sensitive objects are exposed to the template layer.

Recommended fix High confidence

Smarty 3.0.0 or later (recommended: latest stable 3.x release)

  1. 1. Identify the current Smarty version in use (check composer.json, include statements, or vendor directory)
  2. 2. Backup the current codebase
  3. 3. Update Smarty to version 3.0.0 or later (preferably the latest stable 3.x version for additional fixes)
  4. 4. Verify the new Smarty version is installed
  5. 5. Test application functionality to ensure the upgrade does not break existing templates
  6. 6. If using a package manager (Composer), run: composer require smarty/smarty:^3.1 (or appropriate version constraint)
Caveat Smarty 3.x has template syntax changes from Smarty 2.x; review Smarty 2→3 migration guide for breaking changes in template syntax and API

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Smarty Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-4723 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-4723 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data