What is the CVSS score of CVE-2025-6729?

CVE-2025-6729 has a CVSS 3.1 base score of 6.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.0%.

Which versions of Paymaster For Woocommerce are affected by CVE-2025-6729?

Organizations using for WordPress is vulnerable to Server-Side Request Forgery in all should be aware of moderate risk from CVE-2025-6729, a server-side request forgery vulnerability rated CVSS 6.4.

How to fix or mitigate CVE-2025-6729?

Within 30 days: Identify affected systems running for WordPress is vulnerable to Server-Side Request Forgery i and apply vendor patches as part of regular patch cycle. Monitor vendor channels for patch availability.

Paymaster For Woocommerce CVE-2025-6729

EUVD-2025-19922 MEDIUM

Server-Side Request Forgery (SSRF) (CWE-918)

2025-07-04 security@wordfence.com

WordPress SSRF Paymaster For Woocommerce PHP

6.4

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

6.4 MEDIUM

AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

EUVD ID Assigned

Mar 16, 2026 - 02:42 euvd

EUVD-2025-19922

Analysis Generated

Mar 16, 2026 - 02:42 vuln.today

CVE Published

Jul 04, 2025 - 03:15 nvd

MEDIUM 6.4

DescriptionCVE.org

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.

Analysis

Technical ContextAI

Server-Side Request Forgery allows an attacker to induce the server to make HTTP requests to arbitrary destinations, including internal services. This vulnerability is classified as Server-Side Request Forgery (SSRF) (CWE-918).

RemediationAI

Validate and whitelist allowed URLs and IP ranges. Block requests to internal/private IP ranges. Use network segmentation to limit server-side request scope.