CVE-2022-38148
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSilverstripe silverstripe/framework through 4.11 allows SQL Injection.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in Silverstripe silverstripe/framework through version 4.11 allows attackers to inject malicious SQL queries through unsanitized input in database operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 4.11.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed silverstripe/framework versionRun 'composer show silverstripe/framework' or inspect the version in your composer.lock file under silverstripe/frameworkAffected if The installed version is 4.11.0 or lower
-
Identify custom database query codeSearch the codebase for direct database query patterns such as 'Query::create()', 'SQLSelect', 'DB::query()', or 'DB::preparedQuery()' calls that handle user-supplied dataAffected if Custom database queries exist that pass request parameters directly into SQL without using the ORM or parameter binding
-
Review data manipulation methods using raw inputSearch for usages of 'where()', 'filter()', or 'limit()' on DataList queries where the filter values come directly from $_GET, $_POST, or URL parameters without sanitizationAffected if Query methods receive unsanitized user input from request variables
-
Check for raw SQL execution in controllers or servicesSearch for files in src/ or mysite/ containing direct SQL execution (DB::getConn()->query, \SilverStripe\ORM\DB::query) with interpolated variables from user inputAffected if Raw SQL is executed with string-concatenated user input rather than parameterized queries
You are affected if silverstripe/framework version is 4.11.0 or lower AND your codebase contains custom database queries or data manipulation that passes unsanitized user input directly into SQL statements.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade silverstripe/framework to a version beyond 4.11 where the vulnerability has been patched, and conduct code review of database query handling to identify and remediate unsanitized user input.
silverstripe/framework 4.12.0 or later
- 1. Backup your entire SilverStripe project and database before making any changes
- 2. Update your composer.json to require silverstripe/framework version 4.12.0 or higher
- 3. Run 'composer update silverstripe/framework' to install the fixed version
- 4. Clear SilverStripe caches by deleting the contents of the cache directory (usually 'silverstripe-cache' or 'var/cache')
- 5. Run /dev/build?flush=1 to rebuild the database schema
- 6. Test your application thoroughly to verify the SQL injection vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38148 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-38148 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data