GHSA-fv4m-5j2c-787r is a critical-severity (CVSS 9.8) SQL Injection vulnerability in bacula-web/bacula-web. 2 public exploit references exist, so weaponization risk is real. A fix is available for bacula-web/bacula-web — see the affected versions and patch details below.
Bacula-web SQL Injection Vulnerabilities
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-fv4m-5j2c-787r plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
bacula-web/bacula-webReal-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
Bacula-web before 8.0.0-rc2 is affected by multiple SQL Injection vulnerabilities that could allow an attacker to access the Bacula database and, depending on configuration, escalate privileges on the server.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | bacula-web/bacula-web | all versions | 8.0.0-rc2composer require bacula-web/bacula-web:^8.0.0-rc2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Bacula-Web < 8.0.0-rc2 - SQL Injection
by Gustavo Sorondo · Mar 9, 2018
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bacula-web/bacula-web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update bacula-web/bacula-web to 8.0.0-rc2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fv4m-5j2c-787r 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-fv4m-5j2c-787r can be triaged on real exposure rather than presence alone.
Tailored to GHSA-fv4m-5j2c-787r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-fv4m-5j2c-787r in your dependencies?
O3 Security finds GHSA-fv4m-5j2c-787r across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.