dbcve.org
Paymaster For WoocommerceWordPress extension · Qazomardok

CVE-2025-6729

MEDIUM · 6.4 CVSS v3.1 Published 2025-07-04
Fix available
A fix is available. Upgrade to after 0.4.31 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable 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 PayMaster for WooCommerce plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 0.4.31 via the 'wp_ajax_paym_status' AJAX action This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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 PayMaster for WooCommerce plugin for WordPress contains an Server-Side Request Forgery (SSRF) vulnerability in the wp_ajax_paym_status AJAX action affecting all versions up to 0.4.31. Authenticated attackers with Subscriber-level access or higher can cause the server to make arbitrary HTTP requests to internal or external locations, potentially enabling information disclosure or interaction with internal services.

MitigationUpdate the PayMaster for WooCommerce plugin to version 0.4.32 or later to remediate the SSRF vulnerability. Until updated, restrict AJAX endpoint access via server-side controls or disable the plugin if immediate patching is not feasible.

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
Paymaster For WoocommerceWordPress extension
Affected:<= 0.4.31

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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 PayMaster for WooCommerce plugin is installed
    Navigate to WordPress admin > Plugins and look for 'PayMaster for WooCommerce' by Qazomardok in the installed plugins list
    Affected if The plugin appears in the installed plugins list
  2. Check the installed plugin version
    In WordPress admin > Plugins, find PayMaster for WooCommerce and click to view the plugin details, or check the plugin's main PHP file (usually in wp-content/plugins/paymaster-for-woocommerce/) for the Version header in the plugin comment block
    Affected if The version displayed is 0.4.31 or lower
  3. Confirm the vulnerable AJAX endpoint exists
    Check if the file handling the wp_ajax_paym_status action exists in the plugin directory, or attempt to access the endpoint via a simple HTTP request to yoursite.com/wp-admin/admin-ajax.php?action=paym_status
    Affected if The AJAX action paym_status is registered and responds to requests
  4. Verify authenticated user access is possible
    Check if any user roles exist on the site with Subscriber-level access or higher by navigating to WordPress admin > Users > All Users
    Affected if There are any user accounts with Subscriber, Contributor, Author, Editor, or Administrator roles

If the plugin version is 0.4.31 or lower and the wp_ajax_paym_status AJAX endpoint is accessible to authenticated users with Subscriber-level access or higher, the environment is affected by this SSRF vulnerability.

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.

From vendor data
Upgrade available Upgrade to a release after 0.4.31
Interim mitigation

Update the PayMaster for WooCommerce plugin to version 0.4.32 or later to remediate the SSRF vulnerability. Until updated, restrict AJAX endpoint access via server-side controls or disable the plugin if immediate patching is not feasible.

Fix this in Paymaster For Woocommerce Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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