CVE-2025-39381
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Kiotviet KiotViet Sync allows Stored XSS. This issue affects KiotViet Sync: from n/a through 1.8.4.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability in KiotViet Sync versions up to 1.8.4 allows attackers to trick authenticated users into submitting malicious requests that result in stored Cross-Site Scripting (XSS). The lack of proper CSRF token validation enables attackers to craft requests on behalf of victims that inject persistent malicious scripts into the application.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Identify if KiotViet Sync is installedCheck your application for the KiotViet Sync plugin, extension, or module. This may appear in your plugin list, application settings, or installed components depending on your deployment.Affected if KiotViet Sync is present in the environment
-
Determine the installed version of KiotViet SyncLocate the version number for KiotViet Sync. This is typically shown in the plugin/extension details page, in a version file within the installation directory, or in your software inventory if managed centrally.Affected if The installed version cannot be determined or is 1.8.4 or lower
-
Compare the version to the affected rangeReview the identified version against the affected range: versions 1.8.4 and below are vulnerable. Any version up to and including 1.8.4 is affected by this CSRF-to-stored-XSS flaw.Affected if The installed version is 1.8.4 or lower
-
Verify if authenticated user sessions are activeDetermine whether the application supports authenticated user sessions that can submit state-changing requests. CSRF requires authenticated users to inadvertently send requests, so check if user authentication and session handling are enabled.Affected if User authentication is enabled and the application accepts state-changing requests from authenticated users
A user is affected if KiotViet Sync version 1.8.4 or lower is installed and the application processes authenticated user requests, as this combination allows the CSRF-to-stored-XSS attack chain to execute.
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 anti-CSRF tokens for all state-changing operations and apply proper input validation and output encoding to prevent stored XSS. Consider updating to a patched version if available from Kiotviet.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39381 — 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-2025-39381 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