dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-12500

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 Checkout Field Manager (Checkout Manager) for WooCommerce plugin for WordPress is vulnerable to unauthenticated limited file upload in all versions up to, and including, 7.8.1. This is due to the plugin not properly verifying that a user is authorized to perform file upload actions via the "ajax_checkout_attachment_upload" function. This makes it possible for unauthenticated attackers to upload files to the server, though file types are limited to WordPress's default allowed MIME types (images, documents, etc.).

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 Checkout Field Manager for WooCommerce plugin contains an unauthenticated file upload vulnerability in the ajax_checkout_attachment_upload function. The function fails to verify user authentication or authorization before processing file upload requests, allowing any visitor to upload files to the server. While uploads are restricted to WordPress default allowed MIME types (images, documents), this still enables unauthorized file storage on the affected site.

MitigationUpdate the plugin to version 7.8.2 or later which contains proper authorization checks. As an interim measure, disable the plugin or restrict access to the upload functionality via web server rules until a patch can be applied.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Checkout Field Manager for WooCommerce' or check the plugin files in /wp-content/plugins/ for the checkout-field-manager directory.
    Affected if The plugin is not installed or not present in the system.
  2. Identify the installed plugin version
    In WordPress admin Plugins list, click on the plugin name to view details and find the version number. Alternatively, check the main plugin PHP file for the 'Version' header comment in the plugin directory.
    Affected if Unable to determine the version or version is below 7.8.2.
  3. Confirm the vulnerable endpoint is accessible
    Check if the WordPress AJAX endpoint /wp-admin/admin-ajax.php is accessible and responds to the action 'cfm_checkout_attachment_upload'. This can be tested by examining the plugin JavaScript files that enqueue the upload handler, or by reviewing the ajax_checkout_attachment_upload function in the plugin code.
    Affected if The ajax_checkout_attachment_upload function exists and is registered without authentication checks.
  4. Verify file upload functionality is enabled
    Check the plugin settings in WooCommerce > Checkout Fields to see if any field types with file upload capability (such as file upload or image upload fields) are enabled on any checkout form.
    Affected if File upload fields are enabled and accessible to unauthenticated users on the checkout page.

A user is affected if the Checkout Field Manager for WooCommerce plugin is installed with a version earlier than 7.8.2 and the file upload feature is enabled on their checkout forms.

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

Update the plugin to version 7.8.2 or later which contains proper authorization checks. As an interim measure, disable the plugin or restrict access to the upload functionality via web server rules until a patch can be applied.

Recommended fix Moderate confidence

Latest version newer than 7.8.2 (check WordPress Plugin Repository for current release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Checkout Field Manager (Checkout Manager) for WooCommerce'
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, navigate to Dashboard > Updates and select the plugin to update
  6. 6. After updating, verify the plugin is running on a version newer than 7.8.1

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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