dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-11728

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-15
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 Oceanpayment CreditCard Gateway plugin for WordPress is vulnerable to unauthenticated and unauthorized modification of data due to missing authentication and capability checks on the 'return_payment' and 'notice_payment' functions in all versions up to, and including, 6.0. This makes it possible for unauthenticated attackers to update WooCommerce orders to 'failed' status, and update transaction IDs.

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 Oceanpayment CreditCard Gateway WordPress plugin lacks authentication and capability validation on the 'return_payment' and 'notice_payment' callback functions through version 6.0. This allows unauthenticated attackers to directly invoke these functions and manipulate WooCommerce order data, specifically changing order statuses to 'failed' and overwriting transaction IDs.

MitigationUpdate to version 6.1 or later which includes proper authentication checks on payment callback functions; alternatively, implement server-side validation of payment notifications and restrict callback endpoints at the web server level.

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 Oceanpayment CreditCard Gateway plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Oceanpayment CreditCard Gateway' or check the /wp-content/plugins/ directory for the plugin folder
    Affected if The plugin is not found in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, click on the plugin from the Installed Plugins list to view version details, or open the main plugin PHP file and look for the 'Version' header in the plugin comment block
    Affected if Version is 6.0 or earlier (versions 6.1 and later contain the fix)
  3. Confirm WooCommerce is active
    In WordPress admin, go to Plugins > Installed Plugins and verify WooCommerce is active; the vulnerability specifically affects WooCommerce order data manipulation
    Affected if WooCommerce is not active - the specific attack vector targeting order statuses does not apply
  4. Test callback endpoint accessibility
    Attempt to access the callback URLs directly (typically /?wc-api=oceanpayment_return or /?wc-api=oceanpayment_notice) without providing valid authentication tokens; use a tool like curl or a browser to send a request
    Affected if The endpoints return a successful response without requiring authentication or payment validation
  5. Review recent order status changes
    In WooCommerce > Orders, check for any orders with status changed to 'failed' around times you did not expect, or review WooCommerce logs for unexpected calls to the oceanpayment callback functions
    Affected if Orders show unexpected status changes to 'failed' or transaction IDs have been overwritten without corresponding payment activity

Your environment is affected if the Oceanpayment CreditCard Gateway plugin version is 6.0 or earlier AND WooCommerce is active, allowing unauthenticated attackers to manipulate order statuses through the exposed callback functions.

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 to version 6.1 or later which includes proper authentication checks on payment callback functions; alternatively, implement server-side validation of payment notifications and restrict callback endpoints at the web server level.

Recommended fix Moderate confidence

Version 6.1 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Oceanpayment CreditCard Gateway plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version (6.1 or later)
  5. 5. Verify the update completed successfully
  6. 6. Test that WooCommerce order processing still functions correctly with the payment gateway

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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