FlexicaptureApplication · Abbyy

CVE-2018-13793

HIGH · 8.8 CVSS v3.0 Published 2018-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Cross Site Request Forgery (CSRF) vulnerabilities in the HTTP API in ABBYY FlexiCapture before 12 Release 1 Update 7 exist in Web Verification, Web Scanning, Web Capture, Monitoring and Administration, and Login.

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 Cross-Site Request Forgery (CSRF) vulnerabilities exist in the HTTP API of ABBYY FlexiCapture before version 12 Release 1 Update 7. The vulnerabilities affect Web Verification, Web Scanning, Web Capture, Monitoring and Administration, and Login components. Attackers can exploit these by tricking authenticated users into unknowingly submitting malicious requests to the affected API endpoints.

MitigationUpgrade ABBYY FlexiCapture to version 12 Release 1 Update 7 or later, which contains the security fix for these CSRF vulnerabilities.

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.1.263= 12.0.1.267= 12.0.1.282= 12.0.1.292= 12.0.1.367= 12.0.1.428= 12.0.1.475

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 installed ABBYY FlexiCapture version
    Open ABBYY FlexiCapture 12 Administration and Monitoring Console, then go to Help > About, or check the version from the Windows Programs and Features list. Alternatively, check the file version of the main executable (FlexiCapture.exe) in the installation directory.
    Affected if The installed version matches one of these build numbers: 12.0.1.263, 12.0.1.267, 12.0.1.282, 12.0.1.292, 12.0.1.367, 12.0.1.428, or 12.0.1.475
  2. Verify web interface components are enabled
    Check if any of the following web components are enabled in the Administration and Monitoring Console under Application Server > Web Services: Web Verification, Web Scanning, Web Capture, or Monitoring and Administration interfaces.
    Affected if Any of the affected web components (Web Verification, Web Scanning, Web Capture, Monitoring and Administration, or Login) are enabled and accessible over HTTP/HTTPS
  3. Confirm external access to the web API
    Review firewall rules and network configuration to determine if the FlexiCapture web services port (default 80/443 or configured custom port) is exposed to untrusted networks or the internet.
    Affected if The web API endpoints are reachable from untrusted networks, increasing the likelihood of CSRF exploitation against authenticated users

You are affected if the installed ABBYY FlexiCapture version matches any of the specific build numbers (12.0.1.263 through 12.0.1.475) AND the web-based components (Web Verification, Web Scanning, Web Capture, Monitoring/Administration, or Login) are enabled and 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade ABBYY FlexiCapture to version 12 Release 1 Update 7 or later, which contains the security fix for these CSRF vulnerabilities.

Fix this in Flexicapture Scoped from the published advisory
  • Consultation4.0 h
  • Implementation10.0 h
  • Testing6.0 h
  • Review / QA3.0 h
23.0 hours of engineering $4,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-13793 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