How severe is GHSA-jc94-wp59-pq4f?

GHSA-jc94-wp59-pq4f has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-jc94-wp59-pq4f?

GHSA-jc94-wp59-pq4f affects the following packages: baserproject/basercms (Packagist), baserproject/basercms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-jc94-wp59-pq4f?

Update baserproject/basercms to 3.0.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jc94-wp59-pq4f is resolved across your whole dependency graph.

How do I detect GHSA-jc94-wp59-pq4f in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for baserproject/basercms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-jc94-wp59-pq4f if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-jc94-wp59-pq4f?

O3 pinpoints whether GHSA-jc94-wp59-pq4f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-jc94-wp59-pq4f actively exploited in the wild?

No public exploit code has been indexed for GHSA-jc94-wp59-pq4f 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 type of vulnerability is GHSA-jc94-wp59-pq4f?

GHSA-jc94-wp59-pq4f is classified as SQL Injection (CWE-89). 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-jc94-wp59-pq4f published, and has it been updated?

GHSA-jc94-wp59-pq4f was published on May 14, 2022 and was last updated on February 16, 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

CRITICAL severity

GHSA-jc94-wp59-pq4f

CRITICAL

GHSA-jc94-wp59-pq4f is a critical-severity (CVSS 9.8) SQL Injection vulnerability in baserproject/basercms. O3 Security confirms whether GHSA-jc94-wp59-pq4f is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

baserCMS SQL Injection vulnerability

Also known asCVE-2017-10842

Published

May 14, 2022

Updated

Feb 16, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Feb 16, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐘baserproject/basercms🐘baserproject/basercms

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

SQL injection vulnerability in the baserCMS 3.0.14 and earlier, 4.0.5 and earlier allows remote attackers to execute arbitrary SQL commands via unspecified vectors.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`baserproject/basercms`	all versions	3.0.15
🐘Packagist	`baserproject/basercms`	≥ 4.0.0&&< 4.0.6	4.0.6

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for baserproject/basercms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update baserproject/basercms to 3.0.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jc94-wp59-pq4f is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-jc94-wp59-pq4f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-jc94-wp59-pq4f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

SQL injection vulnerability in the baserCMS 3.0.14 and earlier, 4.0.5 and earlier allows remote attackers to execute arbitrary SQL commands via unspecified vectors.

O3 Security · Impact-Aware SCA

Is GHSA-jc94-wp59-pq4f in your dependencies?

O3 detects GHSA-jc94-wp59-pq4f across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works