CVE-2026-12183
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 through 2.10.2 on Linux contains an Improper Authentication vulnerability (CWE-287) in the system configuration module.
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 BUK TS-G Gas Station Automation System versions 2.9.1-2.10.2 has an authentication bypass in /php/ajax-login.php that returns userid=1 (administrator) for any POST request with arbitrary credentials, and privileged endpoints under /php/ajax-main.php and /modules/* lack server-side session validation, allowing full administrative access.
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
- 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 installed versionLocate the BUK TS-G version number in the system login page footer, admin dashboard About section, or configuration files (check common paths like /config/, /settings/, or the main application directory). Compare this version against the affected range 2.9.1-2.10.2.Affected if Installed version is 2.9.1, 2.9.2, 2.9.3, 2.10.0, 2.10.1, or 2.10.2 (any version within 2.9.1-2.10.2 inclusive)
-
Verify ajax-login.php endpoint existsSend a GET request to /php/ajax-login.php and confirm the endpoint responds (even if it returns an error or redirect). Use a tool like curl or browser DevTools to check HTTP response.Affected if The endpoint /php/ajax-login.php is accessible and returns any HTTP response (200, 401, 302, etc.)
-
Test authentication bypassSend a POST request to /php/ajax-login.php with arbitrary username and password (e.g., username: test, password: test). Inspect the response for userid=1 or administrator-level privileges in the returned JSON or session cookie.Affected if The response contains userid=1, admin, or grants authenticated access without valid credentials
-
Check privileged endpoint session validationAfter the bypass test, attempt to access /php/ajax-main.php or any file under /modules/ directory without a legitimate session. Observe whether the endpoint accepts the request or enforces session validation.Affected if Privileged endpoints under /php/ajax-main.php or /modules/ accept requests without proper server-side session validation
You are affected if the installed version is 2.9.1-2.10.2 AND the /php/ajax-login.php endpoint returns administrator privileges (userid=1) for arbitrary credentials, allowing unauthenticated access to administrative functions.
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.
From vendor dataImplement proper credential validation in ajax-login.php with secure session creation, and add server-side session validation to all privileged endpoints under ajax-main.php and /modules/* before allowing administrative actions.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12183 — 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-12183 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