dbcve.org
Samwin AgentApplication · Telecomsoftware

CVE-2013-10003

CRITICAL · 9.8 CVSS v3.1 Published 2022-05-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 vulnerability classified as critical has been found in Telecommunication Software SAMwin Contact Center Suite 5.1. This affects the function getCurrentDBVersion in the library SAMwinLIBVB.dll of the database handler. The manipulation leads to sql injection. The exploit has been disclosed to the public and may be used. Upgrading to version 6.2 is able to address this issue. It is recommended to upgrade the affected component.

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

SQL injection vulnerability in SAMwin Contact Center Suite 5.1 in the getCurrentDBVersion function of SAMwinLIBVB.dll database handler library. Attackers can manipulate SQL queries through this function to access, modify, or delete database contents.

MitigationUpgrade SAMwin Contact Center Suite from version 5.1 to version 6.2 as the vendor has addressed this vulnerability in the newer release.

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
Samwin AgentApplication
Affected:= 5.01.19.06
Samwin Contact CenterApplication
Affected:= 5.1

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 installed SAMwin product and version
    Check the installed software on the system for 'Samwin Agent' or 'Samwin Contact Center' and note the installed version number. This can be done via Windows Programs and Features, registry keys under HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall, or the application's About/Help menu.
    Affected if The installed version is 5.01.19.06 for Samwin Agent, or 5.1 for Samwin Contact Center.
  2. Locate the vulnerable DLL file SAMwinLIBVB.dll
    Search the system for the file SAMwinLIBVB.dll. Common installation paths include C:\Program Files\SAMwin\ or C:\Program Files (x86)\SAMwin\. Use Windows Explorer search or the command 'dir /s /b C:\SAMwinLIBVB.dll' (adjust drive letter as needed).
    Affected if The file SAMwinLIBVB.dll exists on the system and corresponds to the affected product versions.
  3. Verify database connectivity is enabled
    Check the application's configuration or settings to determine if database connectivity is active. This may involve examining configuration files in the SAMwin installation directory (such as .ini, .xml, or .cfg files) that contain database connection parameters.
    Affected if The application is configured to connect to a database, as the SQL injection vulnerability exploits the getCurrentDBVersion function in the database handler library.

A system is affected if it runs Samwin Agent version 5.01.19.06 or Samwin Contact Center version 5.1 with the SAMwinLIBVB.dll library present and database connectivity enabled.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SAMwin Contact Center Suite from version 5.1 to version 6.2 as the vendor has addressed this vulnerability in the newer release.

Recommended fix High confidence

6.2

  1. 1. Backup all current data and configuration files before proceeding with the upgrade
  2. 2. Download SAMwin Contact Center Suite version 6.2 from the official vendor
  3. 3. Upgrade the Samwin Agent and Samwin Contact Center installations to version 6.2
  4. 4. Verify the upgrade was successful by checking the software version
  5. 5. Test that the getCurrentDBVersion function operates correctly without SQL injection vulnerability

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

Fix this in Samwin Agent Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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