CVE-2023-28019
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 · uneditedInsufficient validation in Bigfix WebUI API App site version < 14 allows an authenticated WebUI user to issue SQL queries via an unparameterized SQL query.
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 confidenceSQL injection vulnerability in Bigfix WebUI API App versions prior to 14 allows authenticated WebUI users to execute arbitrary SQL queries through unparameterized SQL queries that lack proper input validation.
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< 14CVSS 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 BigFix WebUI installationLocate the BigFix WebUI installation directory or check for WebUI components on the server (common paths include /opt/BigFix/WebUI or C:\Program Files\BigFix\WebUI)Affected if BigFix WebUI is not installed on the system
-
Determine WebUI API App versionCheck the version of the installed BigFix WebUI API App - typically found in the application manifest, about page, or version file within the WebUI installation directoryAffected if The version is found to be less than 14 (e.g., 13.x, 12.x, etc.)
-
Verify WebUI API endpoint accessibilityConfirm that the WebUI API endpoint is accessible by accessing it via browser or curl command (e.g., https://<server>/webui/api)Affected if The API endpoint is reachable and responds without authentication errors
-
Check WebUI user authentication statusReview the WebUI authentication configuration to determine if user authentication is enabled and functional for the APIAffected if Authenticated WebUI users can access the API interface
A system is affected if BigFix WebUI API App version is installed and is below version 14, with the WebUI API 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 · scoped14
Upgrade Bigfix WebUI API App to version 14 or later to obtain the patched, parameterized SQL query implementation.
BigFix WebUI API App site version 14
- Contact HCL BigFix support or visit support.hcltechsw.com to obtain the BigFix WebUI version 14 upgrade package
- Review upgrade documentation for BigFix WebUI before proceeding
- Back up the current BigFix WebUI configuration and database
- Install the BigFix WebUI API App site version 14
- Verify the upgrade was successful and the SQL injection vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.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 $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28019 — 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-2023-28019 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