CVE-2026-54368
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 · uneditedCentreStack before 17.4 contains a SQL injection vulnerability in GladDBFiles.SearchEx() and SearchExUnder() that allows authenticated attackers to execute arbitrary SQL statements by supplying a crafted x-glad-filter request header through the jsondir API endpoint. Attackers can exploit unsanitized interpolation of the Field parameter directly into SQL query strings to write arbitrary files to the server filesystem via PostgreSQL lo_from_bytea() and lo_export() functions, enabling remote code execution.
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 · high confidenceCentreStack before 17.4 has a SQL injection vulnerability in GladDBFiles.SearchEx() and SearchExUnder() functions. Authenticated attackers can inject arbitrary SQL via the x-glad-filter header through the jsondir API endpoint by exploiting unsanitized interpolation of the Field parameter. This can be chained with PostgreSQL large object functions (lo_from_bytea and lo_export) to write arbitrary files and achieve remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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.
-
Identify CentreStack versionLocate the installed CentreStack version number in the application web interface, about page, or installation documentation. Common locations include the login page footer, admin dashboard, or service information panel.Affected if The installed version is any release prior to 17.4 (e.g., 17.3.x, 17.2.x, earlier)
You are affected if CentreStack version is below 17.4 and the jsondir API endpoint with x-glad-filter header processing is accessible to authenticated users.
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 CentreStack to version 17.4 or later. If immediate upgrade is not possible, implement input validation and parameterized queries for the Field parameter and disable or restrict the PostgreSQL large object functions if not required.
CentreStack version 17.4 or later
- 1. Identify the current CentreStack version by checking the About or System Information section in the CentreStack admin panel
- 2. If the current version is before 17.4, plan for an upgrade to version 17.4 or later
- 3. Before upgrading, perform a complete backup of the CentreStack database and configuration files
- 4. Download the CentreStack version 17.4 (or latest stable release) from the official CentreStack download portal at www.centrestack.com
- 5. Follow the official CentreStack upgrade documentation to apply the update
- 6. After upgrade completion, verify the jsondir API endpoint now properly sanitizes the x-glad-filter header parameter
- 7. Confirm the GladDBFiles.SearchEx() and SearchExUnder() functions no longer allow direct SQL injection through unsanitized Field parameter interpolation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54368 — 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-2026-54368 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