KiotViet Sync Plugin up to 1.8.5 on WordPress authenticated hard-coded password
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in KiotViet Sync Plugin up to 1.8.5 on WordPress. It has been classified as problematic. The impacted element is the function QueryControllerAdmin::authenticated. The manipulation leads to hard-coded password.
This vulnerability is uniquely identified as CVE-2025-12676. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in KiotViet Sync Plugin up to 1.8.5 on WordPress. It has been rated as problematic. This issue affects the function QueryControllerAdmin::authenticated. The manipulation with an unknown input leads to a hard-coded password vulnerability. Using CWE to declare the problem leads to CWE-259. The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
The KiotViet Sync plugin for WordPress is vulnerable to authorizarion bypass in all versions up to, and including, 1.8.5. This is due to the plugin using a hardcoded password for authentication in the QueryControllerAdmin::authenticated function. This makes it possible for unauthenticated attackers to create and sync products.
The advisory is shared at wordfence.com. The identification of this vulnerability is CVE-2025-12676. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/08/2025). MITRE ATT&CK project uses the attack technique T1078.001 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Hard-coded passwordCWE: CWE-259 / CWE-255
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
11/04/2025 Advisory disclosed11/04/2025 VulDB entry created
11/08/2025 VulDB entry last update
Sources
Advisory: wordfence.comStatus: Not defined
CVE: CVE-2025-12676 (🔒)
GCVE (CVE): GCVE-0-2025-12676
GCVE (VulDB): GCVE-100-331217
Entry
Created: 11/04/2025 22:01Updated: 11/08/2025 14:18
Changes: 11/04/2025 22:01 (50), 11/08/2025 14:18 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.