Unauthenticated blind SSRF via unvalidated certificate URL
Published Jul 20, 2026 · Updated Jul 20, 2026
SSRF in Paymenter before 1.5.0 allows remote attackers to trigger blind HTTP GET requests through the PayPal webhook endpoint. The endpoint passes the unvalidated PAYPAL-CERT-URL header directly to file_get_contents, which fetches the attacker-selected URL. No authentication or user interaction is required; no response body is returned, but outbound requests can probe internal services or leak data through side channels.
Summary
What happened
SSRF in Paymenter before 1.5.0 allows remote attackers to trigger blind HTTP GET requests through the PayPal webhook endpoint. The endpoint passes the unvalidated PAYPAL-CERT-URL header directly to file_get_contents, which fetches the attacker-selected URL. No authentication or user interaction is required; no response body is returned, but outbound requests can probe internal services or leak data through side channels.
The record
- CVE
- CVE-2026-44583
- Published
- Jul 20, 2026
- Updated
- Jul 20, 2026
- Vendor
- Paymenter
- Product
- Paymenter
- Classifications
- CWE-918, CAPEC-664, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 20, 2026CVE publishedPublication date reported by the CVE source.
- Jul 20, 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=< 1.5.0
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