dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-12674

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The KiotViet Sync plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the create_media() function in all versions up to, and including, 1.8.5. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 confidence

The KiotViet Sync WordPress plugin lacks file type validation in its create_media() function, allowing unauthenticated attackers to upload arbitrary files to the server. This missing validation permits any file type to be written to the filesystem, which can be leveraged to achieve remote code execution.

MitigationUpgrade to version 1.8.6 or later which contains the fix. If immediate patching is not possible, consider disabling the plugin or implementing web application firewall rules to block suspicious file uploads.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Confirm KiotViet Sync plugin is installed
    Navigate to WordPress admin > Plugins and verify KiotViet Sync appears in the installed plugins list, or check the plugins directory for the kiotviet-sync folder
    Affected if The plugin is installed and active
  2. Identify the installed plugin version
    In WordPress admin > Plugins > KiotViet Sync, click on the plugin name to view the version number displayed in the plugin details, or inspect the plugin's main PHP file header for the Version tag
    Affected if The version is lower than 1.8.6 or the version cannot be determined
  3. Verify the create_media endpoint is accessible
    Check if the WordPress REST API endpoint /wp-json/kiotviet/v1/media is publicly accessible by sending a GET request without authentication
    Affected if The endpoint responds without requiring authentication
  4. Inspect upload directories for unexpected files
    Examine the wp-content/uploads directory and its subdirectories for recently created files with suspicious extensions such as .php, .phtml, .php5, .exe, or .js that were not intentionally uploaded through legitimate WordPress media functions
    Affected if Unexpected executable or script files exist in upload directories, especially with recent modification timestamps

You are affected if the KiotViet Sync plugin is installed with a version lower than 1.8.6 and the create_media REST API endpoint is exposed without authentication.

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

Upgrade to version 1.8.6 or later which contains the fix. If immediate patching is not possible, consider disabling the plugin or implementing web application firewall rules to block suspicious file uploads.

Recommended fix Moderate confidence

Latest version available on wordpress.org (version after 1.8.5)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the KiotViet Sync plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org and upload it via Plugins > Add New > Upload Plugin
  6. 6. Verify the update was successful and the plugin is functioning normally

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
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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