# CVE-2026-1432: SQL injection (SQLi) on the Buroweb platform

> An attacker can execute arbitrary SQL queries via unsanitized parameters in the Buroweb platform to access confidential database information.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2026
- **Updated:** 3 Feb 2026
- **Also known as:** GHSA-hw4f-5c6g-8xfc

## What is CVE-2026-1432?

CVE-2026-1432 is a critical SQL injection vulnerability in T-Systems Buroweb, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-1432?


## How do I fix CVE-2026-1432?

No fix has been published for CVE-2026-1432 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1432 being exploited?

There is no known exploitation of CVE-2026-1432 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1432 and fix it if it is affected.

What it is: CVE-2026-1432 is a critical SQL injection vulnerability in T-Systems Buroweb, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1432 in the wild and no public exploit code.

Affected product: T-Systems Buroweb. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1432/ (Markdown: https://insights.sbomify.com/CVE-2026-1432/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1432
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1432
- OSV: https://osv.dev/vulnerability/CVE-2026-1432

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1432/
Summaries are generated and may contain mistakes; the official description above is the record.