What is the CVSS score of CVE-2018-14716?

CVE-2018-14716 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 33.0%.

Is there a public PoC exploit available for CVE-2018-14716?

Yes, a public proof-of-concept exploit is available for CVE-2018-14716. Prioritise patching immediately. EPSS: 33.0%.

Is there a patch available for CVE-2018-14716?

Yes, a patch is available for CVE-2018-14716. Update the affected software to the latest version immediately.

Seomatic CVE-2018-14716

HIGH

Code Injection (CWE-94)

2018-08-06 cve@mitre.org

Code Injection RCE Seomatic

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Aug 06, 2018 - 20:29 nvd

HIGH 7.5

DescriptionNVD

AnalysisAI

A Server Side Template Injection (SSTI) was discovered in the SEOmatic plugin before 3.1.4 for Craft CMS, because requests that don't match any elements incorrectly generate the canonicalUrl, and can. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as Code Injection (CWE-94), which allows attackers to inject and execute arbitrary code within the application. A Server Side Template Injection (SSTI) was discovered in the SEOmatic plugin before 3.1.4 for Craft CMS, because requests that don't match any elements incorrectly generate the canonicalUrl, and can lead to execution of Twig code. Affected products include: Nystudio107 Seomatic. Version information: before 3.1.4.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Never evaluate user-controlled input as code. Use sandboxing, disable dangerous functions, apply strict input validation.