LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25047: In Smarty before 3.1.47 and 4.x before 4.2.1, libs/plugins/function.mailto.php allows XSS.

In Smarty before 3.1.47 and 4.x before 4.2.1, libs/plugins/function.mailto.php allows XSS. 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-25047 is a cross-site scripting issue in Smarty's mailto plugin. Applications are mainly at risk when they use the plugin and let GET or POST input influence its parameters. This can allow injected JavaScript to run in a user's browser. The source bundle does not show active exploitation.

Executive priority

Treat as a targeted web application cleanup item, not an emergency based on current evidence. Prioritize internet-facing apps using Smarty mailto with user-controlled input, especially customer or admin portals.

Technical view

Smarty before 3.1.47 and 4.x before 4.2.1 have XSS in libs/plugins/function.mailto.php. The condition described is a page using smarty_function_mailto with parameters influenced by GET or POST input. Fixed releases are identified as v3.1.47 and v4.2.1.

Likely exposure

Exposure is likely limited to PHP applications using affected Smarty versions and the mailto plugin with request-controlled parameters. Systems using distro packages should check Debian LTS and Gentoo advisories for packaged fixes.

Exploitation context

The CVE record describes possible JavaScript injection by a user. KEV status is false in the provided bundle, and no cited source in the bundle confirms active exploitation or public weaponization.

Researcher notes

The source bundle lacks CVSS, CWE, and detailed patch notes. Analysis should stay scoped to Smarty mailto XSS and the documented affected version ranges. Do not assume broader Smarty template injection or server-side code execution from these sources.

Mitigation direction

  • Upgrade Smarty 3.x to 3.1.47 or later.
  • Upgrade Smarty 4.x to 4.2.1 or later.
  • Apply Debian LTS or Gentoo security updates where applicable.
  • Avoid request-controlled mailto parameters until fixed.
  • Check upstream and distribution guidance for package-specific remediation.

Validation and detection

  • Inventory deployed Smarty versions in application dependencies.
  • Identify templates or code using smarty_function_mailto.
  • Check whether mailto parameters can come from GET or POST input.
  • Confirm production packages include v3.1.47, v4.2.1, or distro-fixed builds.
  • Regression test affected pages for safe output encoding.
Prepared
Confidence
high
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-25047 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.