/

CVE-2026-12183

Severity:

CRITICAL RISK

(9.8)

Improper Authentication (CWE-287) in BUK TS-G System

CVE-2026-12183

Deferred

Vulnerability type

Category:

Improper Authentication

CWE:

CWE-287, CWE-306

Impact:

Full Administrative Compromise of Gas Station System

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

The BUK TS-G Gas Station Automation System exposes an improper authentication flaw in its configuration module that accepts any credentials as an administrator login.

Because subsequent privileged endpoints do not enforce server-side sessions, a remote unauthenticated attacker can directly invoke administrative actions over fuel equipment and configuration.

Affected context

This vulnerability appears in BUK TS-G Gas Station Automation System deployments running versions 2.9.1 through 2.10.2 on Linux.

It manifests in the web-based system configuration module, specifically around the /php/ajax-login.php, /php/ajax-main.php, and /modules/* endpoints.

Environments where this interface is reachable over the network, especially from untrusted segments, are at heightened risk, as access controls are not reliably enforced server-side.

Exploit preconditions

  • Attack surface: HTTP(S) interface of the configuration module (typically browser-accessible web UI)
  • Required access: Network reachability to /php/ajax-login.php and subsequent privileged endpoints
  • Trigger point: Sending a POST request with arbitrary action=dologin, login, and pwd parameters to the login endpoint, followed by direct calls to admin endpoints
  • Why exploitation is possible: The login endpoint unconditionally returns userid=1 (administrator) for any credentials, and privileged endpoints under /php/ajax-main.php and /modules/* fail to validate a server-side session or enforce authentication/authorization on each request.

Why this happens

The underlying bug class is improper authentication and missing enforcement of authorization checks on sensitive operations.

Instead of verifying user-supplied credentials against a trusted user store and creating a robust, server-side session, the application effectively treats all login attempts as successful administrator logins by returning userid=1.

Compounding this, downstream privileged endpoints execute administrative actions without confirming an authenticated session or user identity, relying implicitly on client-supplied state or none at all.

This behavior maps to CWE-287 (Improper Authentication) and is closely related to CWE-306 (Missing Authentication for Critical Function), as critical configuration and control functions are exposed without reliable, server-enforced authentication.

Potential impact

  • A remote attacker could perform any administrative action available in the configuration module.
  • Attackers may read or modify user rules and permissions.
  • Fuel tank gauge readings and calibration data can be viewed or altered.
  • Control of fuel dispensers, relays, and related hardware can be obtained.
  • Cash registers, bank terminals, and fuel card configurations can be manipulated.
  • Pricing rules, cash collection workflows, and customer display information may be changed.
  • Overall operational integrity, safety controls, and financial data of the gas station automation system can be compromised.

General mitigation guidance

Effective mitigation centers on enforcing robust authentication and authorization for all administrative endpoints.

Common defensive patterns include:

  • Implementing server-side verification of user credentials against a secure identity store before assigning any privileges.
  • Establishing a secure session mechanism (e.g., signed, time-limited session identifiers) and validating this session on every privileged request.
  • Applying role-based access control (RBAC) so that only explicitly authorized accounts can access configuration and control functions.
  • Ensuring that critical operations, especially those affecting physical devices or financial data, require explicit authentication and cannot be triggered solely by crafted HTTP requests.
  • Isolating the administration interface onto restricted network segments and limiting access through firewalls or VPNs to reduce exposure.

How teams detect issues like this

Detection generally involves a combination of code-level review and operational monitoring:

  • Static analysis or manual code review can look for login handlers that unconditionally assign administrator identities or fail to check credentials.
  • Review privileged endpoints for absence of checks on server-side sessions or user roles, especially under /php/ajax-main.php and /modules/*.
  • Implement logging and security monitoring for anomalous administrative activity, such as unexpected configuration changes or control actions from unfamiliar IP addresses.
  • Use web application security scanners or automated test harnesses to probe authentication workflows and verify that invalid credentials are rejected and that privileged endpoints cannot be accessed without a valid session.

Sources

SourceLink
bukts.rubukts.ru/repo-bukts-current
cwe.mitre.orgcwe.mitre.org/data/definitions/287.html
cwe.mitre.orgcwe.mitre.org/data/definitions/306.html
github.comgithub.com/ciprobe/bukts_auth_bypass

Frequently asked

questions

Yes. If the web interface of the BUK TS-G configuration module is reachable over the network, an attacker can exploit it remotely without prior access, using only HTTP requests.

The attacker only needs network connectivity to the affected endpoints. No valid credentials or pre-existing accounts are required because any login attempt is effectively treated as administrative.

The safest pattern is to enforce proper server-side authentication and session management: validate user credentials against a trusted store, issue secure session tokens, and verify both identity and authorization for every privileged action. Critical endpoints should refuse requests that lack a valid, authenticated session.

Future prevention relies on adopting secure design patterns for authentication and access control, including centralized auth middleware, consistent session validation, RBAC for administrative operations, and security-focused code reviews. Automated tests and security scans should validate that privileged endpoints are inaccessible without valid authentication and appropriate roles.

Find out what's already
exploitable in your codebase.