dbcve.org
SiteomatApplication · Orpak

CVE-2017-14851

CRITICAL · 9.8 CVSS v3.1 Published 2019-06-03
Fix available
A fix is available. Upgrade to 6.4.414.084 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A SQL injection vulnerability exists in all Orpak SiteOmat versions prior to 2017-09-25. The vulnerability is in the login page, where the authentication validation process contains an insecure SELECT query. The attack allows for authentication bypass.

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 confidence

SQL injection vulnerability in Orpak SiteOmat's login page allows authentication bypass through injection into an insecure SELECT query during the authentication validation process.

MitigationUpdate to SiteOmat version 2017-09-25 or later which contains the vendor patch; ensure all authentication queries use parameterized/prepared statements to prevent SQL injection.

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
SiteomatApplication
Affected:< 6.4.414.084

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Orpak SiteOmat installation
    Locate the SiteOmat web interface by accessing the application's login page via browser or by checking network accessible services on common web ports (80, 443, 8080). Confirm the product is Orpak SiteOmat by checking the page title, header, or favicon.
    Affected if The system is running Orpak SiteOmat web interface accessible over the network.
  2. Check installed SiteOmat version
    Access the SiteOmat administration interface or about page (typically found in system settings or by appending /about, /info, or /version to the web URL). Alternatively, check version information in the installation directory or system information panel if you have server access.
    Affected if The installed version is lower than 6.4.414.084.
  3. Verify login page is exposed
    Confirm the SiteOmat login page (the authentication endpoint) is network-accessible. This is typically the default web root or a login path such as /login, /auth, or the root URL itself.
    Affected if The login page is directly accessible without additional network restrictions.
  4. Confirm authentication uses vulnerable query
    Since this is a SQL injection in the authentication validation SELECT query, you would need to either review source code if available, or test by attempting a SQL injection payload in the username/password fields (e.g., entering a single quote or SQL meta-character).
    Affected if The login form accepts input and processes it through an unauthenticated SELECT query without parameterized statements.

You are affected if Orpak SiteOmat is running and the installed version is below 6.4.414.084 with the login page network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.4.414.084 or later
Fixed in 6.4.414.084
Interim mitigation

Update to SiteOmat version 2017-09-25 or later which contains the vendor patch; ensure all authentication queries use parameterized/prepared statements to prevent SQL injection.

Recommended fix High confidence

6.4.414.084 (released 2017-09-25 or later)

  1. 1. Contact Orpak/SiteOmat vendor to obtain the patched version 6.4.414.084 or later released after 2017-09-25
  2. 2. Schedule a maintenance window for the upgrade
  3. 3. Back up the current SiteOmat database and configuration files
  4. 4. Apply the upgrade following Orpak's official upgrade documentation
  5. 5. Verify the login page is functioning correctly after upgrade
  6. 6. Test that the authentication mechanism is working as expected
  7. 7. Confirm the SQL injection vulnerability is remediated by attempting to reproduce the bypass (or use vulnerability scanning tool)
Caveat Review release notes for any configuration changes or compatibility considerations before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Siteomat Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-14851 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-14851 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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