dbcve.org
SmartyApplication

CVE-2010-4726

HIGH · 10.0 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
Unspecified vulnerability in the math plugin in Smarty before 3.0.0 RC1 has unknown impact and remote attack vectors. NOTE: this might overlap CVE-2009-1669.

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

Unspecified vulnerability in Smarty's math plugin before version 3.0.0 RC1 with CVSS 10 and remote attack vectors. Based on the overlap indication with CVE-2009-1669 (a PHP code injection vulnerability in the {math} plugin), this is likely a critical code injection or remote code execution flaw allowing attackers to execute arbitrary PHP code via specially crafted mathematical expressions.

MitigationUpgrade Smarty to version 3.0.0 RC1 or later to remediate this vulnerability. If upgrading is not immediately feasible, disable or restrict the math plugin functionality as a temporary workaround.

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
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/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 Smarty version
    Locate the Smarty core library file (commonly Smarty.class.php or similar) and check the $smarty->version variable or the version defined in the file header
    Affected if The installed version is 3.0.0 or earlier, or matches 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. Locate the math plugin file
    Search for the math plugin in the Smarty plugins directory (typically in a 'plugins' subfolder under the Smarty installation) - the file is usually named 'function.math.php'
    Affected if The math plugin file exists in the Smarty plugins directory
  3. Search for {math} usage in templates
    Scan template files (.tpl) for the presence of the {math} function call, which appears as {math ...} in templates
    Affected if Templates contain {math} function calls that pass user-controllable parameters
  4. Check plugin security settings
    Inspect the Smarty configuration for security policy settings, specifically look for settings that control plugin execution or the 'php_handling' setting
    Affected if Security settings allow arbitrary PHP code execution through the math plugin or do not restrict the eval() function
  5. Verify eval function availability
    Examine the math plugin source code (function.math.php) to confirm it uses PHP's eval() function to process mathematical expressions
    Affected if The math plugin uses eval() to process the equation parameter without sanitization

You are affected if your Smarty version is 3.0.0 or earlier and your templates use the {math} plugin with user-influenced parameters, allowing arbitrary PHP code injection.

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 RC1 or later to remediate this vulnerability. If upgrading is not immediately feasible, disable or restrict the math plugin functionality as a temporary workaround.

Recommended fix High confidence

Smarty 3.0.0 or later (3.0.0 RC1 was the first fixed release)

  1. 1. Identify the current Smarty version in use by checking your project's dependencies or include files
  2. 2. If using Smarty 1.x (1.0, 1.0a, 1.0b) or any version prior to Smarty 3.0.0 RC1, plan an upgrade to Smarty 3.0.0 or later
  3. 3. Update the Smarty library in your project via Composer (recommended) or manual replacement
  4. 4. Test the math functionality in your templates after upgrading to ensure compatibility
  5. 5. Verify that the application functions correctly with the new Smarty version
Caveat Smarty 3.x has template syntax changes and API differences from Smarty 1.x; review the migration guide and test thoroughly before deploying to production

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

Fix this in Smarty Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-4726 — 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-4726 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