CVE-2026-3843
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 · uneditedNefteprodukttekhnika BUK TS-G Gas Station Automation System 2.9.1 on Linux contains a SQL Injection vulnerability (CWE-89) in the system configuration module. A remote attacker can send specially crafted HTTP POST requests to the /php/request.php endpoint via the sql parameter in application/x-www-form-urlencoded data (e.g., action=do&sql=<query_here>&reload_driver=0) to execute arbitrary SQL commands and potentially achieve remote code execution.
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 confidenceThe Nefteprodukttekhnika BUK TS-G Gas Station Automation System 2.9.1 contains a critical SQL injection vulnerability in the /php/request.php endpoint. The sql parameter in HTTP POST requests accepts unsanitized user input that is directly used in SQL queries, allowing remote attackers to execute arbitrary SQL commands and potentially achieve remote code execution.
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>= 2.9.1, < 2.10.2CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 the installed BUK TS-G system versionLocate the system version information through the web interface admin panel, system status page, or by checking version files in the application directory. Consult vendor documentation for version retrieval specific to this product.Affected if The installed version is >= 2.9.1 and < 2.10.2
-
Verify the /php/request.php endpoint is accessibleConfirm the web server hosting the BUK TS-G system responds to requests at the /php/request.php path. This may require authentication or be exposed on the local network depending on deployment.Affected if The endpoint is reachable and accepts HTTP requests
-
Check if the sql parameter exists in request.phpExamine the request.php script to determine if it processes a parameter named 'sql'. This can be done by reviewing the source code if accessible or by observing the application's behavior when the parameter is present in requests.Affected if The 'sql' parameter is processed by the endpoint without sanitization
-
Confirm lack of parameterized queriesInspect the request.php code to verify whether SQL queries are constructed using string concatenation or direct parameter insertion rather than prepared statements or parameterized queries.Affected if SQL queries are built using string concatenation with user input rather than parameterized queries
The environment is affected if the BUK TS-G system version is 2.9.1 or higher but below 2.10.2, and the /php/request.php endpoint with the sql parameter is accessible and processes SQL queries without prepared statements.
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 · scoped2.10.2
Implement parameterized queries (prepared statements) for all SQL operations and add input validation/sanitization for the sql parameter. Consider network segmentation to limit exposure of this industrial control system interface.
2.10.2
- Confirm current installed version of Buk Ts G Gas Station Automation System
- Schedule maintenance window for upgrade procedure
- Upgrade to version 2.10.2 or later from the official vendor (bukts.ru)
- After upgrade, verify the /php/request.php endpoint no longer accepts arbitrary SQL via the sql parameter
- Validate that the system configuration module functions correctly post-upgrade
- Monitor system logs for any attempted exploitation attempts during and after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3843 — 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-3843 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