How severe is CVE-2018-25047?

CVE-2018-25047 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2018-25047?

CVE-2018-25047 affects the following packages: smarty/smarty (Packagist), smarty/smarty (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2018-25047?

Update smarty/smarty to 3.1.47 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-25047 is resolved across your whole dependency graph.

How do I detect CVE-2018-25047 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for smarty/smarty, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-25047 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2018-25047 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2018-25047, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-25047?

CVE-2018-25047 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 66th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2018-25047?

CVE-2018-25047 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2018-25047 published, and has it been updated?

CVE-2018-25047 was published on September 15, 2022 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2018-25047 — smarty

MEDIUMFix: smarty-php/smarty@55ea25d

CVE-2018-25047 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in smarty/smarty. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for smarty/smarty — see the affected versions and patch details below.

Smarty Cross-site Scripting vulnerability in pages that use smarty_function_mailto

Also known asGHSA-hwq7-5vv9-c6cf

Published

Sep 15, 2022

Updated

Oct 20, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs66th percentile — riskier than 66% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐘smarty/smarty🐘smarty/smarty

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

In Smarty before 3.1.47 and 4.x before 4.2.1, libs/plugins/function.mailto.php allows cross-site scripting. A web page that uses smarty_function_mailto, and that could be parameterized using GET or POST input parameters, could allow injection of JavaScript code by a user.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`smarty/smarty`	all versions	3.1.47`composer require smarty/smarty:^3.1.47`
🐘Packagist	`smarty/smarty`	≥ 4.0.0&&< 4.2.1	4.2.1`composer require smarty/smarty:^4.2.1`

Affected Products

2 products · 3 configurations

debian linuxdebian

1 version

10.0

Application

smartysmarty

≥ 4.0.0 && < 4.2.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In Smarty before 3.1.47 and 4.x before 4.2.1, libs/plugins/function.mail…

github.comNVDSep 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for smarty/smarty, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update smarty/smarty to 3.1.47 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-25047 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

UbuntuMEDIUM

USN-7158-1Ubuntu

Frequently Asked Questions

In Smarty before 3.1.47 and 4.x before 4.2.1, `libs/plugins/function.mailto.php` allows cross-site scripting. A web page that uses `smarty_function_mailto`, and that could be parameterized using GET or POST input parameters, could allow injection of JavaScript code by a user.

O3 Security · Impact-Aware SCA

Is CVE-2018-25047 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

smarty

3.9/10

Code-Review1/10

Maintained5/10

Branch-Protection0/10

Assessed Oct 26, 2026

Timeline

Disclosed

Sep 15, 2022

First exploit

Sep 16, 2022

2 days after disclosure — rapid exploitation

Last updated

Oct 20, 2026

Identifiers

CVE-2018-25047

GHSA-hwq7-5vv9-c6cf

References

Advisorygithub.com · v3.1.47 Advisorygithub.com · v4.2.1 Advisorylists.debian.org · msg00002 Advisorysecurity.gentoo.org · 202209 09 Advisorynvd.nist.gov · CVE 2018 25047 Fixgithub.com Reportbugs.gentoo.org Weblists.debian.org · msg00013 Webgithub.com · 55ea25d1f50f0406fb1ccedd212c527977793fc9 Webgithub.com · CVE 2018 25047.yaml Packagegithub.com · smarty

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting smarty/smarty are rated as high or higher (top: high).

CVE-2026-62993CVE-2026-62992CVE-2026-62996CVE-2024-35226CVE-2023-28447CVE-2022-29221CVE-2014-8350CVE-2012-4437

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026