Authenticated SSRF via unchecked AJAX URL
Published Aug 29, 2022 · Updated Aug 3, 2024
Server-side request forgery in Mailchimp for WooCommerce before 2.7.1 allows remote authenticated users to scan internal services through AJAX. The mailchimp_woocommerce_oauth_status action accepts an attacker-controlled URL, issues a server-side POST without restricting its destination, and returns the response body. Subscriber-level WordPress access is sufficient, and returned content can disclose reachable internal services; no data-write impact is reported.
Summary
What happened
Server-side request forgery in Mailchimp for WooCommerce before 2.7.1 allows remote authenticated users to scan internal services through AJAX. The mailchimp_woocommerce_oauth_status action accepts an attacker-controlled URL, issues a server-side POST without restricting its destination, and returns the response body. Subscriber-level WordPress access is sufficient, and returned content can disclose reachable internal services; no data-write impact is reported.
The record
- CVE
- CVE-2022-2267
- Published
- Aug 29, 2022
- Updated
- Aug 3, 2024
- Vendor
- Mailchimp
- Product
- Mailchimp for WooCommerce
- Classifications
- CWE-918, CAPEC-664, T1046
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 29, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=2.7.1 <2.7.1
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
- WPScan authenticated SSRF proof of conceptproof of concept · validated
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