Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-12677: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in mykiot KiotViet Sync

0
Medium
VulnerabilityCVE-2025-12677cvecve-2025-12677cwe-200
Published: Wed Nov 05 2025 (11/05/2025, 07:27:55 UTC)
Source: CVE Database V5
Vendor/Project: mykiot
Product: KiotViet Sync

Description

The 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.

AI-Powered Analysis

AILast updated: 11/12/2025, 08:08:25 UTC

Technical Analysis

The vulnerability identified as CVE-2025-12677 affects the KiotViet Sync plugin for WordPress, specifically all versions up to and including 1.8.5. The issue lies within the register_api_route() function located in kiotvietsync/includes/public_actions/WebHookAction.php, which improperly exposes sensitive information. This flaw allows unauthenticated attackers to retrieve the webhook token value configured in the plugin. Webhook tokens are critical secrets used to authenticate and validate webhook requests between systems, and their exposure can lead to unauthorized actions or data exfiltration through forged webhook calls. The vulnerability is classified under CWE-200, indicating exposure of sensitive information to unauthorized actors. The CVSS v3.1 base score is 5.3, with vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, meaning the attack can be performed remotely without privileges or user interaction, and the impact is limited to confidentiality loss without affecting integrity or availability. No patches or known exploits are currently available, but the risk remains due to the sensitive nature of the token. The vulnerability affects all plugin versions, suggesting a systemic design flaw in the API route's access control or data handling. Organizations using this plugin in WordPress environments should be aware of the risk of token leakage, which could facilitate further attacks or unauthorized access to integrated systems relying on these webhooks.

Potential Impact

For European organizations, the exposure of webhook tokens can lead to unauthorized access to backend systems or services integrated via these webhooks. While the vulnerability does not directly compromise data integrity or system availability, the leaked tokens could be used to impersonate legitimate webhook requests, potentially triggering unauthorized operations such as data modification, order processing, or system configuration changes. This risk is particularly significant for e-commerce businesses or service providers relying on KiotViet Sync for inventory or order synchronization. The confidentiality breach could also lead to compliance issues under GDPR if personal data is indirectly exposed or manipulated through unauthorized webhook calls. The medium severity rating reflects that while the immediate impact is limited, the potential for chained attacks or data leakage exists. Organizations with high dependency on WordPress plugins for business-critical operations are at greater risk. Additionally, the lack of authentication or user interaction requirements lowers the barrier for exploitation, increasing the threat surface.

Mitigation Recommendations

To mitigate this vulnerability, organizations should immediately review and restrict access to the vulnerable API route in the KiotViet Sync plugin. Implementing IP whitelisting or authentication mechanisms for API endpoints can prevent unauthorized token extraction. Monitoring web server logs for unusual access patterns to the register_api_route() endpoint is advisable to detect potential exploitation attempts. Until an official patch is released, consider disabling the KiotViet Sync plugin if feasible or isolating the WordPress instance from public access. Additionally, rotate any exposed webhook tokens to invalidate compromised credentials. Organizations should also ensure that their WordPress installations and plugins are regularly updated and subscribe to vendor security advisories for timely patch application. Employing Web Application Firewalls (WAFs) with custom rules to block suspicious API requests targeting this plugin can provide an additional layer of defense.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-03T22:04:56.746Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 690afea4da9019f6f26cbdf9

Added to database: 11/5/2025, 7:37:08 AM

Last enriched: 11/12/2025, 8:08:25 AM

Last updated: 2/6/2026, 3:20:59 PM

Views: 84

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats