Skip to content
Fencer Intel
high 8.8

GHSA-xx4r-5265-48j6 json

silverstripe/framework SQL injection in full text search

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

When performing a fulltext search in SilverStripe 4.0.0 the 'start' querystring parameter is never escaped safely. This exposes a possible SQL injection vulnerability.

The issue exists in 3.5 and 3.6 but is less vulnerable, as SearchForm sanitises these variables prior to passing to mysql.

Patch / fix

  • packagist silverstripe/framework 3.5.6, 3.6.3, 4.0.1

Is GHSA-xx4r-5265-48j6 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
>=3.5.0-rc1, <3.5.6
>=3.6.0-rc1, <3.6.3
>=4.0.0-rc1, <4.0.1
3.5.6
3.6.3
4.0.1

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.