dbcve.org
FlexicaptureApplication · Abbyy

CVE-2018-13792

CRITICAL · 9.8 CVSS v3.1 Published 2019-02-10
Fix available
A fix is available. Upgrade to 12.0.2.1194 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
Multiple SQL injection vulnerabilities in the monitoring feature in the HTTP API in ABBYY FlexiCapture before 12 Release 2 allow an attacker to execute arbitrary SQL commands via the mask, sortOrder, filter, or Order parameter.

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

Multiple SQL injection vulnerabilities exist in the HTTP API monitoring feature of ABBYY FlexiCapture before version 12 Release 2. Attackers can execute arbitrary SQL commands through the mask, sortOrder, filter, or Order parameters in the monitoring API.

MitigationUpgrade ABBYY FlexiCapture to Release 2 or later to obtain the patched version. If immediate patching is not possible, restrict network access to the HTTP API monitoring endpoints as a temporary compensating control.

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
FlexicaptureApplication
Affected:>= 12.0, < 12.0.2.1194

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. Verify ABBYY FlexiCapture is installed
    Check for the product in Windows Programs and Features, or look for the installation directory (commonly C:\Program Files\ABBYY FlexiCapture 12\), or check for the FlexiCapture Monitoring Service in Windows Services.
    Affected if The product is present on the system
  2. Identify the installed version
    Open the FlexiCapture Monitoring (FCMonitoring) service properties and check the executable path, or check the version of exe files in the installation directory. The version format is typically 12.0.x.x.
    Affected if The installed version is 12.0.x where x is less than 12.0.2.1194, or specifically any version >= 12.0 and < 12.0.2.1194
  3. Confirm the HTTP API monitoring feature is enabled
    Check if the FlexiCapture Monitoring Service (FCMonitoring) is running and if port 8080 (default monitoring port) is listening. Use command: netstat -an | findstr 8080
    Affected if The monitoring service is running and port 8080 is open and listening
  4. Test for exposed monitoring API endpoints
    Attempt to access the monitoring API endpoints via HTTP, for example: http://localhost:8080/Monitoring/api/monitoring?mask=test or similar paths containing the vulnerable parameters (mask, sortOrder, filter, Order).
    Affected if The monitoring API responds to requests containing these parameters, indicating the vulnerable endpoints are accessible

A system is affected if ABBYY FlexiCapture 12.0 through 12.0.2.1193 is installed with the HTTP monitoring service enabled and accessible, as the SQL injection flaw exists in the monitoring API feature.

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 12.0.2.1194 or later
Fixed in 12.0.2.1194
Interim mitigation

Upgrade ABBYY FlexiCapture to Release 2 or later to obtain the patched version. If immediate patching is not possible, restrict network access to the HTTP API monitoring endpoints as a temporary compensating control.

Recommended fix High confidence

12.0.2.1194 or later (FlexiCapture 12 Release 2)

  1. Download ABBYY FlexiCapture 12 Release 2 (version 12.0.2.1194 or later) from the official ABBYY downloads page at www.abbyydownloads.com
  2. Install the upgrade following ABBYY's standard upgrade procedure for FlexiCapture
  3. Verify the monitoring feature HTTP API no longer accepts SQL injection via the mask, sortOrder, filter, or Order parameters

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

Fix this in Flexicapture Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-13792 — 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-2018-13792 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