How severe is CVE-2017-15367?

CVE-2017-15367 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-15367?

CVE-2017-15367 affects the following packages: bacula-web/bacula-web (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2017-15367?

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 CVE-2017-15367 is resolved across your whole dependency graph.

How do I detect CVE-2017-15367 in my Packagist dependencies?

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.

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

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2017-15367 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2017-15367, including 1 documented proof-of-concept exploit on Exploit-DB and 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-2017-15367?

CVE-2017-15367 has an EPSS (Exploit Prediction Scoring System) score of 23.1%, placing it in the 98th 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 warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2017-15367?

CVE-2017-15367 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 CVE-2017-15367 published, and has it been updated?

CVE-2017-15367 was published on March 7, 2018 and was last updated on October 20, 2026. 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

CVE-2017-15367 — bacula-web

CRITICALFix: bacula-web/bacula-web@90d4c44

CVE-2017-15367 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in bacula-web/bacula-web. 2 public exploit or proof-of-concept references are indexed, 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

Also known asGHSA-fv4m-5j2c-787r

Published

Mar 7, 2018

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

23.1%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘bacula-web/bacula-web

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

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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`bacula-web/bacula-web`	all versions	8.0.0-rc2`composer require bacula-web/bacula-web:^8.0.0-rc2`

Affected Products

1 product · 2 configurations

Application

bacula-webbacula

≤ 7.4.0

1 version

8.0.0

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.

EDB-44272webappsphp

Bacula-Web < 8.0.0-rc2 - SQL Injection

by Gustavo Sorondo · Mar 9, 2018

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
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 CVE-2017-15367 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-15367 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-89SQL Injection

Weaponization

No Nuclei template or Metasploit module yet. 2 public proof-of-concept references are listed on this page.

Timeline

Disclosed

Mar 7, 2018

First exploit

Mar 9, 2018

1 day after disclosure — rapid exploitation

Last updated

Oct 20, 2026

Identifiers

CVE-2017-15367

GHSA-fv4m-5j2c-787r

References

Advisorybacula-web.org · bacula web 8 0 0 rc2 Advisorynvd.nist.gov · CVE 2017 15367 Fixgithub.com · 90d4c44a0dd0d65c6fb3ab2417b83d700c8413ae Reportbugs.bacula-web.org · view Webweb.archive.org · bacula web 8 0 0 rc2 Webweb.archive.org · view Webexploit-db.com Packagegithub.com · bacula web Evidenceexploit-db.com

Related vulnerabilities

Also affects bacula-web/bacula-web

This CVE is critical severity — higher than any of the other 1 CVE affecting bacula-web/bacula-web (highest there: high).

CVE-2025-45346

Same weakness: CWE-89

This CVE is critical severity; 1 of 7 other CVEs with CWE-89 is rated as high or higher (top: critical).

CVE-2026-44265CVE-2026-33944CVE-2026-115324CVE-2026-107375CVE-2026-107385CVE-2026-107384CVE-2026-60090Browse all CWE-89

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2017-15367 — bacula-web

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2017-15367 in your dependencies?