CVE-2025-12677
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 · uneditedThe KiotViet Sync plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.8.5 via the register_api_route() function in kiotvietsync/includes/public_actions/WebHookAction.php. This makes it possible for unauthenticated attackers to extract the webhook token value when configured.
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 confidenceThe KiotViet Sync WordPress plugin up to version 1.8.5 exposes the configured webhook token through the register_api_route() function in WebHookAction.php. Unauthenticated attackers can extract this token value, potentially gaining access to the KiotViet API integration.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Verify KiotViet Sync plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and check if 'KiotViet Sync' appears in the list. Note the installed version number shown.Affected if Plugin is installed and version is 1.8.5 or earlier
-
Locate WebHookAction.php fileAccess the WordPress site filesystem via FTP, file manager, or SSH. Navigate to wp-content/plugins/kiotviet-sync/includes/ or similar path and locate WebHookAction.php.Affected if File exists in the plugin directory
-
Inspect register_api_route() for token exposureOpen WebHookAction.php and examine the register_api_route() function. Look for any code that returns, echoes, or includes the webhook token value in the API response without authentication checks.Affected if The code shows the webhook token being returned or exposed in the API route response
-
Test API route accessibilityUse a tool like curl or a browser to make a request to the plugin's webhook endpoint (typically /?rest_route=/kiotviet-sync/v1/webhook or similar). Observe if the response contains the token value without providing any credentials.Affected if The API route returns the token value to unauthenticated requests
A user is affected if the KiotViet Sync plugin version is 1.8.5 or earlier AND the WebHookAction.php file exposes the webhook token in an unauthenticated API response.
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 dataUpdate the KiotViet Sync plugin to the latest version once available, or if no update exists, modify the WebHookAction.php code to ensure the webhook token is not exposed in API route responses.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12677 — 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-12677 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