Authenticated SSRF via paym_status AJAX action
Published Jul 4, 2025 · Updated Apr 8, 2026
Server-side request forgery in PayMaster for WooCommerce 0.4.31 and earlier allows remote authenticated users to access internal services. The wp_ajax_paym_status AJAX action takes an attacker-controlled destination and makes the WordPress host request it, but the request-building code is not public. Subscriber-level access is sufficient to query or modify information exposed by reachable internal services, with no reported service interruption.
Summary
What happened
Server-side request forgery in PayMaster for WooCommerce 0.4.31 and earlier allows remote authenticated users to access internal services. The wp_ajax_paym_status AJAX action takes an attacker-controlled destination and makes the WordPress host request it, but the request-building code is not public. Subscriber-level access is sufficient to query or modify information exposed by reachable internal services, with no reported service interruption.
The record
- CVE
- CVE-2025-6729
- Published
- Jul 4, 2025
- Updated
- Apr 8, 2026
- Vendor
- Qazomardok
- Product
- PayMaster for WooCommerce
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 4, 2025CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.4.31
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo