How broadly exploitable is this vulnerability in real applications?

Exploitability depends on whether an attacker can influence the callback arrays passed into Locutus' `call_user_func_array` or `call_user_func`. If callbacks are constructed directly or indirectly from user input (including request parameters, serialized structures, or configuration they can modify), the issue can often be exploited to run arbitrary JavaScript. If callbacks are entirely static and never derived from untrusted data, practical risk is lower but still warrants fixing due to future code changes.

What level of access does an attacker need to exploit this?

An attacker typically needs the ability to submit or manipulate data that flows into the callback array parameters. This might be through a web form, API endpoint, query parameter, or other input surface that your application uses when calling these Locutus functions. They do not need direct access to the server or codebase—just control over the data that reaches the vulnerable eval path.

What is the safest general fix pattern for this issue?

The safest pattern is to eliminate dynamic evaluation entirely: do not use `eval()` or similar constructs for function dispatch. Instead, operate on real function references, or resolve method names via controlled lookups into a whitelist of allowed call targets. Ensure callback arrays are strongly validated for type and content, rejecting anything outside expected structures.

Severity:

HIGH RISK

(8.1)

Eval Injection (CWE-95) in Locutus call_user_func_array JavaScript Implementation

CVE-2026-29091

Published:

Mar 6, 2026

Status:

Received

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-78

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

Remote Code Execution

March 7, 2026

CWE-89

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Remote Code Execution via SQL Injection on the Database Server

March 7, 2026

Vulnerability Type

Category:

Eval Injection / Code Injection

CWE:

CWE-95

Impact:

Remote Code Execution in JavaScript Runtime

Severity:

HIGH RISK

(8.1)

CVSS Version:

3.1

Vulnerability Type

Category:

Eval Injection / Code Injection

CWE:

CWE-95

Impact:

Remote Code Execution in JavaScript Runtime

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 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Eval Injection (CWE-95) in Locutus call_user_func_array JavaScript Implementation

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

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare