CVE-2026-62993: CWE-918: Server-Side Request Forgery (SSRF) in smarty-php smarty
Description
Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. Prior to 4.5.7 and 5.8.2, depending on the release line, Smarty's {fetch} handling in libs/plugins/function.fetch.php and src/FunctionHandler/Fetch.php used Security::isTrustedUri() to validate only the initial remote URL against trusted_uri when a security policy was active. For resources handled by file_get_contents(), including HTTPS URLs, PHP followed HTTP redirects by default. An attacker who could supply or influence a fetch target and had an open redirect on a trusted host could redirect the request to an attacker-chosen internal endpoint, bypass the trusted_uri allowlist, and perform server-side request forgery. This issue is fixed in versions 4.5.7 and 5.8.2.
CVSS v4.0
Score 6.9medium
Affected software
smarty-php
smarty
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Smarty's {fetch} function in versions before 4.5.7 and 5.8.2 uses Security::isTrustedUri() to validate only the initial URL when a security policy is active. However, PHP's file_get_contents() follows HTTP redirects by default, which allows an attacker who can influence the fetch target and exploit an open redirect on a trusted host to redirect the request to an attacker-controlled internal endpoint. This bypasses the trusted URI allowlist and results in a server-side request forgery (CWE-918). The vulnerability is addressed by updating to Smarty 4.5.7 or 5.8.2.
Potential Impact
An attacker able to control or influence the fetch target in Smarty can exploit an open redirect on a trusted host to perform SSRF attacks, potentially accessing internal network resources that should be protected by the trusted URI allowlist. This could lead to unauthorized internal resource access or information disclosure. The CVSS 4.0 base score is 6.9 (medium severity).
Mitigation Recommendations
This vulnerability is fixed in Smarty versions 4.5.7 and 5.8.2. Users should upgrade to these versions or later to remediate the issue. No other official remediation or temporary fixes are documented. Patch status is confirmed by the vendor advisory embedded in the description.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-14T23:10:57.031Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a95ed25acd9273b49971376
Added to database: 08/31/2026, 21:07:49 UTC
Last enriched: 09/07/2026, 13:37:11 UTC
Last updated: 10/15/2026, 06:48:17 UTC
Views: 96
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.