How severe is GHSA-2p96-p7qh-4rgr?

No CVSS score has been assigned to GHSA-2p96-p7qh-4rgr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2p96-p7qh-4rgr?

GHSA-2p96-p7qh-4rgr affects the following packages: github.com/plentico/plenti (Go). Ecosystems affected: Go.

How do I fix GHSA-2p96-p7qh-4rgr?

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 GHSA-2p96-p7qh-4rgr is resolved across your whole dependency graph.

How do I detect GHSA-2p96-p7qh-4rgr 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 GHSA-2p96-p7qh-4rgr if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-2p96-p7qh-4rgr actively exploited in the wild?

No public exploit code has been indexed for GHSA-2p96-p7qh-4rgr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-2p96-p7qh-4rgr?

GHSA-2p96-p7qh-4rgr has an EPSS (Exploit Prediction Scoring System) score of 2.7%, placing it in the 86th 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 GHSA-2p96-p7qh-4rgr?

GHSA-2p96-p7qh-4rgr is classified as CWE-74 (CWE-74), OS Command Injection (CWE-78). 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.

Is there exploit tooling available for GHSA-2p96-p7qh-4rgr?

A Nuclei detection template exists for GHSA-2p96-p7qh-4rgr, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-2p96-p7qh-4rgr published, and has it been updated?

GHSA-2p96-p7qh-4rgr was published on October 31, 2024 and was last updated on October 31, 2024. 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

Plenti arbitrary file write vulnerabilityGHSA-2p96-p7qh-4rgr

GHSA-2p96-p7qh-4rgr is a CWE-74 vulnerability in github.com/plentico/plenti. A fix is available for github.com/plentico/plenti — see the affected versions and patch details below.

Also known asCVE-2024-49380GO-2024-3213

Published

Oct 31, 2024

Updated

Oct 31, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2p96-p7qh-4rgr.

EPSS Exploitation Probability

via FIRST.org ↗

2.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs86th percentile — riskier than 86% 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 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 Code Execution. 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

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 GHSA-2p96-p7qh-4rgr is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

How to detect GHSA-2p96-p7qh-4rgr

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-2p96-p7qh-4rgr -u https://target

Template: Plenti < v0.7.2 - OS Command Injection
Severity: critical
Impact: Unauthenticated attackers can write arbitrary files to the server, potentially achieving remote code execution.
Remediation: Update Plenti to version 0.7.2 or later.

Template by ProjectDiscovery nuclei-templates (iamnoooob, rootxharsh, pdresearch), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

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 Code Execution. Version 0.7.2 fixes the vulnerability.

O3 Security · Impact-Aware SCA

Is GHSA-2p96-p7qh-4rgr in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works