dbcve.org
TopmeetingApplication

CVE-2019-13409

CRITICAL · 9.8 CVSS v3.1 Published 2019-10-17
Fix available
A fix is available. Upgrade to 8.8 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 was discovered in TOPMeeting before version 8.8 (2019/08/19). An attacker can use a union based injection query string though a search meeting room feature to get databases schema and username/password.

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

A union-based SQL injection vulnerability exists in the search meeting room feature of TOPMeeting versions before 8.8. The vulnerability is located in the query string parameter, allowing attackers to inject arbitrary SQL queries to extract sensitive database information including the database schema, usernames, and plaintext passwords.

MitigationUpgrade TOPMeeting to version 8.8 or later. Until patched, implement input validation and migrate to parameterized queries to prevent SQL injection attacks.

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
TopmeetingApplication
Affected:< 8.8

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 Topmeeting installation and version
    Locate the Topmeeting installation directory and check for version information in version files, about pages, or application metadata. Common locations include the installation folder, config files, or the application header/footer.
    Affected if Installed version is below 8.8 (any version string less than 8.8 or where version cannot be determined but the product is present)
  2. Confirm the search meeting room feature is accessible
    Access the Topmeeting web interface and navigate to the meeting room search functionality. Check if the feature is enabled in the application configuration or menu options.
    Affected if The search meeting room feature is exposed and accessible to users or unauthenticated attackers
  3. Verify query string parameter handling in search
    Examine the application's handling of search requests. Intercept a search request using a proxy tool and inspect whether the meeting room search accepts input via query string parameters (URL parameters).
    Affected if The application accepts and processes user-supplied input through query string parameters in the meeting room search without sanitization
  4. Test for SQL injection susceptibility
    Submit a test query string with SQL metacharacters (such as single quote ', union select, or boolean-based payloads) in the search parameter to observe application response behavior.
    Affected if The application returns database errors, displays unexpected data, or behaves differently when SQL metacharacters are submitted, indicating unsanitized input is passed to the database

If Topmeeting is installed with a version below 8.8 AND the meeting room search feature is accessible AND the application processes query string parameters without proper sanitization, the environment is affected by this SQL injection vulnerability.

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

Upgrade TOPMeeting to version 8.8 or later. Until patched, implement input validation and migrate to parameterized queries to prevent SQL injection attacks.

Recommended fix High confidence

Topmeeting version 8.8

  1. Backup the Topmeeting application database and configuration files before proceeding with the upgrade.
  2. Download Topmeeting version 8.8 or later from the official vendor repository.
  3. Stop the Topmeeting service to prevent active connections during upgrade.
  4. Install the new version (8.8) following the vendor's standard upgrade procedure.
  5. Restart the Topmeeting service.
  6. Verify the upgrade was successful by checking the version number in the application interface.
  7. Test the search meeting room feature to confirm the SQL injection vulnerability is no longer present.
  8. Ensure the application is functioning normally with all features working as expected.

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

Fix this in Topmeeting Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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