CVE-2019-13190
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 · uneditedIn Knowage through 6.1.1, the sign up page does not invalidate a valid CAPTCHA token. This allows for CAPTCHA bypass in the signup page.
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 confidenceKnowage through version 6.1.1 has a CAPTCHA bypass vulnerability in the signup page. The system fails to invalidate CAPTCHA tokens after successful validation, allowing reuse of the same token multiple times. This enables automated bot registrations and potential account abuse.
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<= 6.1.1CVSS 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
- None
- Integrity
- None
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 Knowage versionAccess the Knowage administration panel or check the application metadata (typically found in the 'About' section, version info in the login page footer, or in the application's WAR/package metadata)Affected if Version is 6.1.1 or lower
-
Verify signup page accessibilityNavigate to the user registration/signup endpoint (commonly /knowage/ nebo/servlet/ or /knowage/restful-services/registrazione) in your Knowage instanceAffected if Signup page is publicly or internally accessible
-
Identify CAPTCHA implementationInspect the signup page source code or network traffic to locate the CAPTCHA mechanism (look for CAPTCHA session tokens, image endpoints, or validation AJAX calls)Affected if CAPTCHA is present on the signup form
-
Test CAPTCHA token reuseSubmit the same CAPTCHA token value multiple times in succession on the signup page (capture the token from one CAPTCHA generation and reuse it across multiple registration attempts without requesting a new CAPTCHA)Affected if The same CAPTCHA token is accepted for multiple registration submissions (vulnerability present)
-
Check CAPTCHA session invalidationReview server-side logs or session storage during repeated CAPTCHA validation attempts to see if the token is tracked as consumed after first useAffected if No server-side invalidation occurs after successful CAPTCHA validation (token remains valid for reuse)
Your environment is affected if running Knowage version 6.1.1 or lower AND the signup page is accessible AND CAPTCHA tokens can be reused across multiple registration attempts without being invalidated.
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 one-time-use logic for CAPTCHA tokens by invalidating them immediately after successful validation, either through server-side session tracking or token consumption logging.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13190 — 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-2019-13190 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