CVE-2018-13791
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 · uneditedThe HTTP API in ABBYY FlexiCapture before 12 Release 1 Update 7 allows an attacker to conduct Access Control attacks via the /FlexiCapture12/Login/Server/SevaUserProfile FlexiCaptureTmsSts2 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 · moderate confidenceABBYY FlexiCapture before version 12 Release 1 Update 7 contains an access control vulnerability in its HTTP API. The issue is located in the /FlexiCapture12/Login/Server/SevaUserProfile endpoint with the FlexiCaptureTmsSts2 parameter, which allows attackers to bypass authorization checks and potentially access sensitive functionality or data.
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= 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.475CVSS 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.0/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.
-
Determine installed FlexiCapture versionCheck the application's About or Help section, or inspect the installed binaries (FlexiCapture.exe or FlexiCapture12.Web.exe) by right-clicking and viewing Properties > Details to see the File Version. Alternatively, check the Windows Programs and Features list for the installed version number.Affected if The installed version matches one of the affected builds: 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, or is any version earlier than 12 Release 1 Update 7.
-
Verify HTTP API is enabledConfirm that the FlexiCapture Web server component (FlexiCapture12 Web Server) is installed and running. Check IIS Manager for the FlexiCapture12 website/application pool, or look for the FlexiCapture12 Web site binding in IIS.Affected if The FlexiCapture12 web interface or HTTP API is enabled and accessible.
-
Check network exposure of the APIReview firewall rules, IIS bindings, and network configuration to determine if the FlexiCapture12 web endpoints are reachable from untrusted networks. Use netstat or Test-NetConnection to identify listening ports (typically 80 or 443 for the web API).Affected if The /FlexiCapture12/ Login/Server/SevaUserProfile endpoint is exposed to the internet or untrusted internal networks.
-
Inspect the specific vulnerable endpointAttempt a GET or POST request to http(s)://<server>/FlexiCapture12/Login/Server/SevaUserProfile and observe whether the application responds (even with an error) versus rejecting the request outright. Check IIS logs for access attempts to this endpoint.Affected if The endpoint responds to requests, indicating the API is active and potentially vulnerable to the authorization bypass.
You are affected if FlexiCapture 12 is installed with any version earlier than Release 1 Update 7 AND the HTTP API/web interface is enabled and accessible to untrusted users.
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.
dbcve · scopedApply ABBYY FlexiCapture 12 Release 1 Update 7 or later to patch the access control vulnerability. Restrict network access to the HTTP API endpoints until the patch can be applied.
ABBYY FlexiCapture 12 Release 1 Update 7 or later
- 1. Verify current FlexiCapture installation version by checking the application or control panel
- 2. Download ABBYY FlexiCapture 12 Release 1 Update 7 or later from the official ABBYY downloads portal (abbyydownloads.com)
- 3. Create a complete backup of the current FlexiCapture database and configuration files
- 4. Stop all FlexiCapture services before beginning the upgrade process
- 5. Run the installer for the new version, following the on-screen prompts
- 6. After installation completes, verify that all services start correctly
- 7. Test the /FlexiCapture12/Login/Server/SevaUserProfile endpoint to confirm the access control vulnerability is resolved
- 8. Verify that existing workflows and integrations function properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13791 — 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-2018-13791 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