dbcve.org
Duitku Payment GatewayWordPress extension · Duitku

CVE-2024-0631

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-13
Fix available
A fix is available. Upgrade to after 2.11.4 or later.
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 Duitku Payment Gateway plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the check_duitku_response function in all versions up to, and including, 2.11.6. This makes it possible for unauthenticated attackers to change the payment status of orders to failed.

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 Duitku Payment Gateway WordPress plugin has a broken access control vulnerability in the check_duitku_response function. This function lacks a capability check, allowing any unauthenticated user to invoke it and arbitrarily change order payment statuses to 'failed' without proper authorization.

MitigationUpdate the plugin to version 2.11.7 or later, which should include proper capability checks on the check_duitku_response function to ensure only authorized users can modify payment statuses.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Duitku Payment GatewayWordPress extension
Affected:<= 2.11.4

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. Check installed Duitku Payment Gateway plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > locate Duitku Payment Gateway and read the version number displayed under the plugin name, or inspect the main plugin file header for the Version field
    Affected if The displayed version number is 2.11.4 or lower
  2. Confirm the plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify that Duitku Payment Gateway shows as 'Active' under the plugin status
    Affected if The plugin is active and the version is <= 2.11.4 - the vulnerability is only exploitable when the plugin is enabled
  3. Verify unauthenticated access to check_duitku_response function exists
    Inspect the plugin source code, specifically the check_duitku_response function, and confirm it lacks add_action or add_hook calls with capability checks like current_user_can or manage_options before processing payment status changes
    Affected if The check_duitku_response function processes requests without verifying user capabilities, allowing any visitor to trigger it

You are affected if the Duitku Payment Gateway plugin is active and the installed version is 2.11.4 or lower, as this version lacks capability checks on the check_duitku_response function allowing unauthenticated status changes.

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
Upgrade available Upgrade to a release after 2.11.4
Interim mitigation

Update the plugin to version 2.11.7 or later, which should include proper capability checks on the check_duitku_response function to ensure only authorized users can modify payment statuses.

Recommended fix High confidence

Duitku Payment Gateway version 2.11.7 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find the Duitku Payment Gateway plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version (2.11.7 or higher)
  5. 5. Verify the update completed successfully
  6. 6. Test that the payment gateway functionality still works correctly

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

Fix this in Duitku Payment Gateway Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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