Quick answers
- Is CVE-2026-3843 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-3843 being exploited in the wild.
- How severe is CVE-2026-3843?
- Critical severity, with a CVSS score of 9.8, published 10 March 2026.
- Which products and versions are affected?
- Nefteprodukttekhnika BUK TS-G 2.9.1.
- Is there a fix for CVE-2026-3843?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-3843 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-3843?
- Check whether you run Linux Kernel or Nefteprodukttekhnika BUK TS-G at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a SQL injection (CWE-89) in the system configuration module accessible via the /php/request.php endpoint. An unauthenticated remote attacker can send HTTP POST requests with specially crafted SQL commands in the 'sql' parameter (e.g., action=do&sql=<query_here>&reload_driver=0) using application/x-www-form-urlencoded encoding to execute arbitrary SQL statements against the backend database. Successful exploitation allows an attacker to read, modify, or delete database records, potentially escalate to remote code execution depending on database permissions and the underlying system configuration. The vulnerability affects BUK TS-G 2.9.1 running on Linux; patch status should be verified with the vendor.
Affected products
- Nefteprodukttekhnika BUK TS-G 2.9.1
Timeline
- 2026-03-10: disclosed: CVE-2026-3843 published
- 2025-11: other: Vulnerability likely existed in earlier versions; repository data shows active development