How severe is GHSA-v4cp-2q7v-hg9q?

No CVSS score has been assigned to GHSA-v4cp-2q7v-hg9q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v4cp-2q7v-hg9q?

GHSA-v4cp-2q7v-hg9q affects the following packages: remdex/livehelperchat (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-v4cp-2q7v-hg9q?

Update remdex/livehelperchat to 4.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v4cp-2q7v-hg9q is resolved across your whole dependency graph.

How do I detect GHSA-v4cp-2q7v-hg9q in my Packagist dependencies?

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

How do I mitigate GHSA-v4cp-2q7v-hg9q 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-v4cp-2q7v-hg9q actively exploited in the wild?

No public exploit code has been indexed for GHSA-v4cp-2q7v-hg9q 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-v4cp-2q7v-hg9q?

GHSA-v4cp-2q7v-hg9q has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 74th 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-v4cp-2q7v-hg9q?

GHSA-v4cp-2q7v-hg9q is classified as OS Command Injection (CWE-78). This weakness type 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 GHSA-v4cp-2q7v-hg9q published, and has it been updated?

GHSA-v4cp-2q7v-hg9q was published on February 29, 2024 and was last updated on December 1, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

livehelperchat Server-Side Template InjectionGHSA-v4cp-2q7v-hg9q

Fix: LiveHelperChat/livehelperchat@a61d231

GHSA-v4cp-2q7v-hg9q is a OS Command Injection vulnerability in remdex/livehelperchat. A fix is available for remdex/livehelperchat — see the affected versions and patch details below.

Also known asCVE-2024-27516

Published

Feb 29, 2024

Updated

Dec 1, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 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-v4cp-2q7v-hg9q.

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐘remdex/livehelperchat

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

Description

Server-Side Template Injection (SSTI) vulnerability in livehelperchat before 4.34v, allows remote attackers to execute arbitrary code and obtain sensitive information via the search parameter in lhc_web/modules/lhfaq/faqweight.php.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`remdex/livehelperchat`	all versions	4.29`composer require remdex/livehelperchat:^4.29`

Affected Products

1 product · 1 configurations

Application

live helper chatlivehelperchat

< 4.34

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for remdex/livehelperchat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update remdex/livehelperchat to 4.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v4cp-2q7v-hg9q 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.

Frequently Asked Questions

Server-Side Template Injection (SSTI) vulnerability in livehelperchat before 4.34, allows remote attackers to execute arbitrary code and obtain sensitive information via the search parameter in lhc_web/modules/lhfaq/faqweight.php.

O3 Security · Impact-Aware SCA

Is GHSA-v4cp-2q7v-hg9q in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works