# CVE-2022-2267: MailChimp for Woocommerce < 2.7.1 - Subscriber+ SSRF

> Logged-in users can trigger server-side requests to internal networks, enabling private network scanning and data access.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-c7c8-3594-h7vm

## What is CVE-2022-2267?

CVE-2022-2267 is a medium-severity server-side request forgery vulnerability in Unknown Mailchimp for WooCommerce, published on 29 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Mailchimp for WooCommerce WordPress plugin before 2.7.1 has an AJAX action that allows any logged in users (such as subscriber) to perform a POST request on behalf of the server to the internal network/LAN, the body of the request is also appended to the response so it can be used to scan private network for example

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2022-2267?

It affects 1 product.


Products: Mailchimp Mailchimp for Woocommerce.

## How do I fix CVE-2022-2267?

No fix has been published for CVE-2022-2267 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-2267 being exploited?

There is no known exploitation of CVE-2022-2267 in the wild and no public exploit code.

## Other vulnerabilities in Unknown Mailchimp for WooCommerce

- [CVE-2022-2556](https://insights.sbomify.com/CVE-2022-2556/): MailChimp for Woocommerce < 2.7.2 - Admin+ SSRF (low 2.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2267 and fix it if it is affected.

What it is: CVE-2022-2267 is a medium-severity server-side request forgery vulnerability in Unknown Mailchimp for WooCommerce, published on 29 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2267 in the wild and no public exploit code.

Affected product: Unknown Mailchimp for WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-2267/ (Markdown: https://insights.sbomify.com/CVE-2022-2267/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-2267
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-2267
- OSV: https://osv.dev/vulnerability/CVE-2022-2267

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-2267/
Summaries are generated and may contain mistakes; the official description above is the record.