dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-1432

CRITICAL · 9.3 CVSS v4.0 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
SQL injection vulnerability in the Buroweb platform version 2505.0.12, specifically in the 'tablon' component. This vulnerability is present in several parameters that do not correctly sanitize user input in the endpoint '/sta/CarpetaPublic/doEvent?APP_CODE=STA&PAGE_CODE=TABLON'. Exploiting this vulnerability could allow an attacker to execute queries on the database and gain access to confidential information.

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 confidence

SQL injection vulnerability in Buroweb platform version 2505.0.12 within the 'tablon' component at endpoint '/sta/CarpetaPublic/doEvent?APP_CODE=STA&PAGE_CODE=TABLON'. Multiple parameters fail to properly sanitize user input, allowing attackers to inject arbitrary SQL queries and access confidential database information.

MitigationImplement parameterized queries or prepared statements for all database interactions in the affected endpoint and parameters. Apply input validation and escaping for user-supplied data before incorporating it into 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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:L/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Buroweb platform installation
    Locate Buroweb installation directories and identify version information in configuration files, manifest files, or application metadata. Common locations include installation directories, version files, or the application's main configuration.
    Affected if Buroweb platform version 2505.0.12 is installed
  2. Verify the installed version against affected range
    Compare the installed Buroweb version to version 2505.0.12. Check version files, build manifests, or administrative panels that display the platform version.
    Affected if Installed version matches exactly 2505.0.12 (or falls within the 2505.0.x lineage if additional affected versions are disclosed)
  3. Confirm 'tablon' component is present and enabled
    Inspect the application's module or component directory for the 'tablon' component. Check configuration files or the application dashboard to determine if this component is actively loaded/enabled.
    Affected if The 'tablon' component is present and enabled in the Buroweb installation
  4. Check access to the vulnerable endpoint
    Verify that the endpoint '/sta/CarpetaPublic/doEvent?APP_CODE=STA&PAGE_CODE=TABLON' is accessible within the application. This may require reviewing URL routing configuration or attempting to access the endpoint directly if the application is exposed.
    Affected if The '/sta/CarpetaPublic/doEvent' endpoint with 'TABLON' page code is accessible and processes requests
  5. Inspect SQL query handling in the tablon component
    Examine the source code or decompiled classes for the tablon component, specifically looking at how parameters are incorporated into SQL queries at the affected endpoint. Look for direct string concatenation of user input into SQL statements without parameterized queries.
    Affected if User-supplied parameters are directly concatenated into SQL queries without proper sanitization or use of prepared statements

A user is affected if Buroweb platform version 2505.0.12 is installed, the 'tablon' component is enabled, and the vulnerable endpoint '/sta/CarpetaPublic/doEvent' with TABLON page code processes unsanitized SQL parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries or prepared statements for all database interactions in the affected endpoint and parameters. Apply input validation and escaping for user-supplied data before incorporating it into SQL queries.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1432 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1432 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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