dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-32573

HIGH · 8.5 CVSS v3.1 Published 2025-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Kiotviet KiotViet Sync allows SQL Injection. This issue affects KiotViet Sync: from n/a through 1.8.3.

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 confidence

SQL injection vulnerability in KiotViet Sync allows attackers to inject malicious SQL commands through unsanitized input, potentially enabling unauthorized data access, modification, or deletion.

MitigationRemediate by implementing parameterized queries or prepared statements for all database interactions, validating and sanitizing user inputs, and applying principle of least privilege to database accounts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify KiotViet Sync installation
    Check if KiotViet Sync software is installed on the system by looking for its executable or service. On Windows, check Program Files or services list; on Linux, check /opt or standard application directories.
    Affected if KiotViet Sync is found installed on the system
  2. Identify installed version
    Run the application with version flag (commonly --version or -v) or check the software's About section, manifest file, or installed packages listing.
    Affected if Installed version matches or falls within any affected version range for this CVE (compare to vendor advisories)
  3. Check database connectivity configuration
    Locate configuration files (often config.json, settings.xml, or .env files in the application directory) and examine database connection strings or ORM configuration settings.
    Affected if Database connection is configured and the application uses direct SQL queries without parameterized queries
  4. Inspect sync feature settings
    Examine the sync module configuration files or admin panel settings for KiotViet Sync to identify how user input flows into database queries.
    Affected if Sync feature is enabled and accepts external input that flows to database operations without sanitization
  5. Review API or web interface exposure
    Check if KiotViet Sync exposes any API endpoints, web interfaces, or integration points that accept external input for sync operations.
    Affected if External-facing sync interfaces accept unsanitized input parameters

User is affected if KiotViet Sync is installed and uses unsanitized input in database queries within the sync functionality.

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

Remediate by implementing parameterized queries or prepared statements for all database interactions, validating and sanitizing user inputs, and applying principle of least privilege to database accounts.

Recommended fix Moderate confidence

Version newer than 1.8.3 (contact KiotViet for exact fixed release)

  1. 1. Identify the currently installed KiotViet Sync version in your environment.
  2. 2. Check KiotViet's official release notes or contact KiotViet support to confirm the specific version that addresses CVE-2025-32573.
  3. 3. Plan the upgrade during a maintenance window to minimize business impact.
  4. 4. Back up the current KiotViet Sync installation and its database before upgrading.
  5. 5. Upgrade KiotViet Sync to the version newer than 1.8.3 that includes the security fix.
  6. 6. Verify the upgrade was successful and test that KiotViet Sync functionality remains intact.
  7. 7. Confirm the SQL injection vulnerability is resolved by reviewing KiotViet's patch notes or release documentation.
Caveat Review KiotViet release notes for any breaking changes between 1.8.3 and the target upgrade version

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

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