CVE-2026-25773
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 · unedited** UNSUPPORTED WHEN ASSIGNED ** Focalboard version 8.0 fails to sanitize category IDs before incorporating them into dynamic SQL statements when reordering categories. An attacker can inject a malicious SQL payload into the category id field, which is stored in the database and later executed unsanitized when the category reorder API processes the stored value. This Second-Order SQL Injection (Time-Based Blind) allows an authenticated attacker to exfiltrate sensitive data including password hashes of other users. NOTE: Focalboard as a standalone product is not maintained and no fix will be issued.
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 confidenceFocalboard 8.0 contains a second-order SQL injection (time-based blind) in the category reorder API. Unsanitized category IDs are stored in the database and later executed as dynamic SQL when the reorder function processes them, allowing authenticated attackers to exfiltrate sensitive data including password hashes.
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= 8.0.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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed Focalboard versionCheck the Focalboard version by inspecting the application binary, package manifest, or version endpoint (e.g., GET /api/v1/version or checking the main binary with --version flag). Compare against the affected version 8.0.0.Affected if The installed version is exactly 8.0.0
-
Verify category reorder API existsConfirm the category reorder API endpoint exists by reviewing Focalboard routing configuration or API documentation. Typical endpoint pattern: PUT /api/v1/teams/{team_id}/categories/reorderAffected if The category reorder API endpoint is present and accessible in the deployment
-
Check for SQL injection logs or database anomaliesReview application logs for time-based SQL injection indicators (unusual query execution times, SQL syntax errors in category-related operations, or database connection anomalies). Inspect the database query logs if available.Affected if Logs show suspicious time delays in category operations or SQL error messages containing category ID values
-
Inspect database for injected payloads in category tablesQuery the categories table directly (e.g., SELECT id, name FROM categories WHERE id LIKE '%SELECT%' OR id LIKE '%SLEEP%' OR id LIKE '%UNION%') to detect any SQL injection payloads stored as category IDs.Affected if Category ID fields contain SQL keywords, functions, or obvious injection payloads
You are affected if you are running Focalboard version 8.0.0 and the category reorder API 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.
From vendor dataSince Focalboard is unsupported with no official fix, mitigate by deploying a WAF/proxy layer to sanitize category ID inputs, disabling the category reorder functionality if unnecessary, or migrating to an alternative solution.
- Consultation6.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25773 — 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-25773 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