How severe is CVE-2024-49381?

No CVSS score has been assigned to CVE-2024-49381 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-49381?

CVE-2024-49381 affects the following packages: github.com/plentico/plenti (Go). Ecosystems affected: Go.

How do I fix CVE-2024-49381?

Update github.com/plentico/plenti to 0.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-49381 is resolved across your whole dependency graph.

How do I detect CVE-2024-49381 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/plentico/plenti, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-49381 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2024-49381 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2024-49381, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-49381?

CVE-2024-49381 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 55th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-49381?

CVE-2024-49381 is classified as CWE-74 (CWE-74), Path Traversal (CWE-22). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2024-49381 published, and has it been updated?

CVE-2024-49381 was published on October 25, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2024-49381 — plenti

CVE-2024-49381 is a CWE-74 vulnerability in github.com/plentico/plenti. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/plentico/plenti — see the affected versions and patch details below.

Plenti arbitrary file deletion vulnerability

Also known asGHSA-6h8w-hrfp-pffxGO-2024-3214

Published

Oct 25, 2024

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-49381.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/plentico/plenti

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Plenti, a static site generator, has an arbitrary file deletion vulnerability in versions prior to 0.7.2. The /postLocal endpoint is vulnerable to an arbitrary file write deletion when a plenti user serves their website. This issue may lead to information loss. Version 0.7.2 fixes the vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/plentico/plenti`	all versions	0.7.2`go get github.com/plentico/plenti@v0.7.2`

Affected Products

1 product · 1 configurations

Application

plentiplenti

< 0.7.2

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Plenti, a static site generator, has an arbitrary file deletion vulnerab…

securitylab.github.comNVDNov 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/plentico/plenti, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/plentico/plenti to 0.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-49381 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2024-49381 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works