Cyber Resilience

CVE-2024-49380

RCE in Plenti ≤ 0.7.2

Public PoCRCECommand Injection
Published
25 October 2024
Modified
06 May 2025
Patch / advisory
View advisory
CVSS Score v4 8.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.027 85th percentile
Risk Priority 70 floored blend · peak EPSS

Summary

CVE-2024-49380 is a high-severity Injection (CWE-74) vulnerability in Plenti Plenti. Its CVSS base score is 8.9 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 15% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

Plenti, a static site generator, contains an arbitrary file write vulnerability in versions prior to 0.7.2. The flaw resides in the /postLocal endpoint that becomes reachable whenever a user runs the built-in website server, and it is tracked under CWE-74 and CWE-78. Successful exploitation can result in remote code execution, reflected in the CVSS 4.0 score of 8.9.

An unauthenticated network attacker can send crafted requests to the endpoint and write arbitrary files to the underlying filesystem. Because the write occurs in the context of the running Plenti process, an attacker can place executable content or configuration files that lead to code execution on the host.

The issue is resolved in release 0.7.2. The project’s GitHub advisory and corresponding code change in serve.go document the fix and recommend that sites running the development server upgrade immediately.

The EPSS score is currently 0.7146 at its observed peak, indicating notable exploitation interest since disclosure.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

Plenti, a static site generator, has an arbitrary file write vulnerability in versions prior to 0.7.2. The `/postLocal` endpoint is vulnerable to an arbitrary file write vulnerability when a plenti user serves their website. This issue may lead to Remote…

more

Code Execution. Version 0.7.2 fixes the vulnerability.

CWE(s)
CWE-74CWE-78

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1059.003 Windows Command Shell Execution
Adversaries may abuse the Windows command shell for execution.
attack.mitre.org →
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1221 Template Injection Stealth
Adversaries may create or modify references in user document templates to conceal malicious code or force authentication attempts.
attack.mitre.org →
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-49381Same product: Plenti Plenti
CVE-2023-31209Shared CWE-74, CWE-78
CVE-2026-55427Shared CWE-74, CWE-78
CVE-2024-10919Shared CWE-74, CWE-78
CVE-2023-35895Shared CWE-74, CWE-78
CVE-2021-38294Shared CWE-74, CWE-78
CVE-2024-10914Shared CWE-74, CWE-78
CVE-2024-10915Shared CWE-74, CWE-78
CVE-2023-23749Shared CWE-74
CVE-2023-48835Shared CWE-74

Affected Assets

plenti
plenti
≤ 0.7.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.1
  • V1.2.3
  • V1.2.5
  • V1.2.8

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing or incorrect command sanitization during development.

SI-10 Information Input Validation good match

SI-10 directly requires validation of information inputs to reject malformed or special-element content before it reaches downstream parsers.

AC-6 Least Privilege partial match

Least privilege reduces the permissions available to any process that could be subverted by injected commands.

CM-7 Least Functionality partial match

Least functionality restricts available OS commands and interpreters, limiting the blast radius of injection.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require proper neutralization of untrusted input before command construction.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and output encoding that prevent injection flaws.

PR.PS-02 partial match
prevents

Routine patching/maintenance can remediate known command-injection CVEs in dependencies (partial forward) but does nothing to stop developers from introducing improper neutralization in custom code (none reverse).

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches injection vulnerabilities before release.

A.8.15 Logging partial match
finds

Logging supports detection of injection attempts but does not prevent the weakness.

A.8.16 Monitoring activities partial match
finds

Monitoring activities can identify active injection attacks after they occur.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and output encoding that directly prevent injection flaws.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against injection attacks in software design.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce injection surfaces but do not prescribe specific neutralization techniques.

References