How broadly exploitable is this vulnerability?

Exploitability depends on whether an attacker can influence environment variables for processes that trigger hotplug_call; in environments where untrusted users or services can affect hotplug events, the risk is significantly higher.

Does an attacker need local access to exploit this issue?

Typically some form of local or adjacent access is required, such as control over a service, script, or interface that can set environment variables before procd invokes hotplug_call, though the exact path depends on the specific OpenWrt configuration.

What is the safest general fix pattern for this kind of bug?

The robust pattern is to implement strict environment sanitization using explicit whitelists, correctly parsing variable names (up to the `=`) and discarding or normalizing sensitive variables before running privileged code, combined with using absolute paths for all critical executables.

Severity:

HIGH RISK

(7.8)

Environment Variable Injection via Faulty Filtering (CWE-269) in OpenWrt hotplug_call

CVE-2026-30874

Published:

Mar 19, 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-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Privilege Escalation via Environment Manipulation

CWE:

CWE-74;CWE-187;CWE-269

Impact:

Privilege Escalation

Severity:

HIGH RISK

(7.8)

CVSS Version:

3.1

Vulnerability Type

Category:

Privilege Escalation via Environment Manipulation

CWE:

CWE-74;CWE-187;CWE-269

Impact:

Privilege Escalation

Severity:

HIGH RISK

(7.8)

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

Environment Variable Injection via Faulty Filtering (CWE-269) in OpenWrt hotplug_call

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.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

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