smarty-php Smarty up to 4.5.6/5.8.1 Fetch function.fetch.php Security::isTrustedUri server-side request forgery

Summaryinfo

A vulnerability categorized as critical has been discovered in smarty-php Smarty up to 4.5.6/5.8.1. This affects the function Security::isTrustedUri of the file libs/plugins/function.fetch.php of the component Fetch. The manipulation results in server-side request forgery. This vulnerability is reported as CVE-2026-62993. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability was found in smarty-php Smarty up to 4.5.6/5.8.1. It has been classified as critical. Affected is the function Security::isTrustedUri of the file libs/plugins/function.fetch.php of the component Fetch. The manipulation with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is available at github.com. This vulnerability is traded as CVE-2026-62993 since 07/15/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit.

By approaching the search of inurl:libs/plugins/function.fetch.php it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 4.5.7 or 5.8.2 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Customer Relationship Management System

Vendor

• smarty-php

Name

• Smarty

Version

• 4.5.0
• 4.5.1
• 4.5.2
• 4.5.3
• 4.5.4
• 4.5.5
• 4.5.6
• 5.8.0
• 5.8.1

License

• commercial

Website

• Product: https://github.com/smarty-php/smarty/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion