dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-12883

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-12
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 Campay Woocommerce Payment Gateway plugin for WordPress is vulnerable to Unauthenticated Payment Bypass in all versions up to, and including, 1.2.2. This is due to the plugin not properly validating that a transaction has occurred through the payment gateway. This makes it possible for unauthenticated attackers to bypass payments and mark orders as successfully completed resulting in a loss of income.

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 Campay Woocommerce Payment Gateway plugin for WordPress fails to validate that payment transactions have actually been processed through the Campay payment gateway. This allows unauthenticated attackers to directly trigger order completion callbacks without any payment, bypassing the entire payment process and marking orders as paid.

MitigationUpdate the plugin to version 1.2.3 or later which includes proper payment gateway validation. Alternatively, disable the plugin until a fix is available.

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. Locate the Campay plugin installation directory
    Check the WordPress plugins folder (wp-content/plugins/) for a directory named 'campay-woocommerce-payment-gateway' or similar Campay-related folder
    Affected if The plugin directory is present on the server
  2. Identify the installed plugin version
    Open the main plugin PHP file and locate the 'Version' field in the plugin header comment, or check the readme.txt file for the version number
    Affected if The version number is lower than 1.2.3 or cannot be determined
  3. Confirm the plugin is active
    Query the WordPress options table (wp_options) for the option 'active_plugins' or check the Plugins admin page to see if Campay payment gateway is enabled
    Affected if The Campay plugin appears in the list of active plugins
  4. Verify the payment callback handler exists
    Search the plugin files for WordPress hooks related to payment notifications (such as 'init', 'wp_ajax', 'rest_api_init', or specific callback function names that handle the Campay webhook)
    Affected if The plugin registers a callback handler for processing payment gateway notifications
  5. Inspect the callback validation logic
    Examine the code in the callback handler file to determine if it validates the payment with the Campay API (look for API calls to Campay, signature verification, or transaction status checks before marking orders as complete)
    Affected if The callback handler marks orders as paid without verifying the payment status through the Campay gateway API

You are affected if the Campay Woocommerce Payment Gateway plugin is installed, active, and the installed version is below 1.2.3, and the payment callback handler lacks proper validation with the Campay payment gateway.

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 1.2.3 or later which includes proper payment gateway validation. Alternatively, disable the plugin until a fix is available.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (likely 1.2.3 or higher, verify on wordpress.org/plugins/campay-woocommerce-payment-gateway/)

  1. Check the WordPress plugin repository or contact the plugin developer to confirm the fixed version is available
  2. Update the Campay Woocommerce Payment Gateway plugin to the latest version available in the WordPress plugin repository
  3. After updating, verify the payment flow works correctly by placing a test order
  4. Ensure WooCommerce is also updated to the latest compatible version
  5. Review any recent orders in WooCommerce for suspicious activity indicating the vulnerability may have been exploited

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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