Skip to content
Fencer Intel
high 8.8

GHSA-265q-222x-52m6 json

silverstripe/framework has potential SQL Injection vulnerability in PostgreSQL database connector

published 2y ago modified last yr.

cvss
8.8
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

A potential SQL injection vulnerability was identified by using the silverstripe/postgresql database adapter. While unlikely to be exploitable, we have patched silverstripe/framework to ensure that table names are safely escaped before being passed to database adapters or user code.

Patch / fix

  • packagist silverstripe/framework 4.0.6, 4.1.4, 4.2.3

Is GHSA-265q-222x-52m6 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
packagist silverstripe/framework
>=4.0.0-rc1, <4.0.6
>=4.1.0-rc1, <4.1.4
>=4.2.0-rc1, <4.2.3
4.0.6
4.1.4
4.2.3

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.