dbcve.org
ServerApplication · Trueconf

CVE-2022-46763

HIGH · 8.8 CVSS v3.1 Published 2022-12-27
Fix available
A fix is available. Upgrade to 5.2.6 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 issue in a database stored function in TrueConf Server 5.2.0.10225 (fixed in 5.2.6.10025) allows a low-privileged database user to execute arbitrary SQL commands as the database administrator, resulting in execution of arbitrary code.

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 SQL injection vulnerability in a database stored function in TrueConf Server versions 5.2.0 through 5.2.5 allows a low-privileged database user to escalate privileges to database administrator and execute arbitrary SQL commands, which can lead to arbitrary code execution on the host system.

MitigationUpgrade TrueConf Server to version 5.2.6.10025 or later to remediate the SQL injection vulnerability.

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
ServerApplication
Affected:< 5.2.6

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Check TrueConf Server version
    Locate and inspect the TrueConf Server version information. This is typically found in the server management interface, about section, or in installation/registry files depending on the deployment method.
    Affected if The installed version is 5.2.0 through 5.2.5 (versions prior to 5.2.6)
  2. Identify the database configuration
    Examine the TrueConf Server configuration to determine which database backend is in use (PostgreSQL, MySQL, or internal database) and how it is accessed.
    Affected if TrueConf Server uses a SQL database backend and the database is accessible to application users
  3. Review database user privileges
    Query the database to list all database users and their assigned roles. Check for any user accounts that have limited or non-administrative privileges.
    Affected if There exists a low-privileged database user account that could be exploited for privilege escalation
  4. Examine stored functions
    Inspect the database for custom stored functions or procedures. Look for functions that accept user-supplied input and could be vulnerable to SQL injection.
    Affected if Custom stored functions exist in the database that accept input parameters without proper sanitization

A TrueConf Server installation is affected if it runs version 5.2.0 through 5.2.5 and uses a database configuration where low-privileged users can interact with vulnerable stored functions.

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

Upgrade TrueConf Server to version 5.2.6.10025 or later to remediate the SQL injection vulnerability.

Recommended fix High confidence

TrueConf Server 5.2.6.10025 or later

  1. Back up the current TrueConf Server configuration and database before upgrading
  2. Download TrueConf Server version 5.2.6.10025 or later from the official vendor website
  3. Stop the TrueConf Server service before applying the upgrade
  4. Install the updated version following the vendor's standard upgrade procedure
  5. Start the TrueConf Server service after installation completes
  6. Verify the upgrade was successful by checking the server version in the admin panel
  7. Confirm the SQL injection vulnerability is resolved by reviewing database user permissions
Caveat Review vendor release notes for any configuration or feature changes between your current version and 5.2.6

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

Fix this in Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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