How broadly exploitable is this vulnerability?

Exploitability depends on whether an attacker can influence `options.imports` key names or achieve prototype pollution that affects objects merged into imports. In applications where these inputs are strictly static and developer-defined, practical exploitability is reduced.

Does an attacker need authenticated access to exploit this issue?

Not inherently. The key requirement is influence over imports key names or prototype pollution, which might be reachable via unauthenticated endpoints in some applications, or only after authentication in others, depending on how `_.template` is exposed.

What is the safest general fix pattern?

The safest approach is to ensure that all `options.imports` keys are static, developer-controlled strings and to eliminate or strictly constrain any code paths where user input can become an imports key. Additionally, refactor templating logic to avoid dynamic function generation where feasible.

Severity:

HIGH RISK

(8.1)

Code Injection via Template Imports (CWE-94) in Lodash _.template

CVE-2026-4800

Published:

Mar 31, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-94

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

Remote Code Execution by authenticated users via malicious file upload

May 10, 2026

CWE-94

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Remote Code Execution by Authenticated Users

May 10, 2026

Vulnerability Type

Category:

Code Injection

CWE:

CWE-94

Impact:

Arbitrary Code Execution within the Application Context

Severity:

HIGH RISK

(8.1)

CVSS Version:

3.1

Vulnerability Type

Category:

Code Injection

CWE:

CWE-94

Impact:

Arbitrary Code Execution within the Application Context

Severity:

HIGH RISK

(8.1)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest that knows every line of it.

Ask AI for summary of CodeAnt

Code Injection via Template Imports (CWE-94) in Lodash _.template

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal