CVE-2026-49490
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 · uneditedOpenCATS from version 0.9.1a contains an SQL injection vulnerability in DataGrid filter handling that allows authenticated attackers to inject SQL through crafted filters targeting the non-filterable Tags column in the Candidates DataGrid. Attackers can bypass column filterable restrictions by manipulating filter requests to execute arbitrary SQL queries against the database.
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 confidenceOpenCATS version 0.9.1a and later contains an SQL injection vulnerability in the DataGrid filter handling. The Tags column in the Candidates DataGrid is designated as non-filterable, but attackers with authenticated access can manipulate filter requests to bypass this restriction and inject arbitrary SQL queries.
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
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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 OpenCATS installation versionCheck the version file or admin interface of your OpenCATS installation. Look for a version identifier in configuration files, an about page, or the login screen footer.Affected if The installed version is 0.9.1a or any later version (0.9.2, 0.9.3, etc.)
-
Verify user authentication is enabledConfirm that your OpenCATS instance requires login credentials. Check if the application has user accounts configured and access controls enforced.Affected if User authentication is required to access the application - the vulnerability requires an authenticated attacker
-
Confirm Candidates module is accessibleLog into OpenCATS and navigate to the Candidates section. Verify that the Candidates DataGrid is accessible and functional for your user account.Affected if The Candidates module is available and loadable in your installation
-
Check if Tags column filtering exists in Candidates DataGridIn the Candidates DataGrid interface, locate the column headers and identify if a Tags column is present with filter functionality enabled.Affected if A Tags column exists in the Candidates DataGrid with filter options that can be manipulated
-
Compare version against affected rangeDocument your exact OpenCATS version number and compare it against the affected range of 0.9.1a and later versions.Affected if The installed version starts at 0.9.1a or is any higher version number
Your environment is affected if OpenCATS version 0.9.1a or later is installed, user authentication is enabled providing attacker access, and the Candidates DataGrid with Tags column filtering is accessible.
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.
From vendor dataImplement strict input validation and use parameterized queries for all DataGrid filter operations to prevent SQL injection; consider temporarily disabling the affected filter functionality until a patch is applied.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49490 — 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-49490 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