# CVE-2022-40700: Server Side Request Forgery (SSRF) vulnerability affecting multiple WordPress plugins

> Attackers can exploit SSRF in multiple WordPress plugins to access internal resources or bypass security controls.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jan 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-3mv9-fmvf-xvmx

## What is CVE-2022-40700?

CVE-2022-40700 is a high-severity server-side request forgery vulnerability in AMO for WP – Membership Management AMP Toolbox, published on 19 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Server-Side Request Forgery (SSRF) vulnerability in Montonio Montonio for WooCommerce, Wpopal Wpopal Core Features, AMO for WP – Membership Management ArcStone wp-amo, Long Watch Studio WooVirtualWallet – A virtual wallet for WooCommerce, Long Watch Studio WooVIP – Membership plugin for WordPress and WooCommerce, Long Watch Studio WooSupply – Suppliers, Supply Orders and Stock Management, Squidesma Theme Minifier, Paul Clark Styles styles, Designmodo Inc. WordPress Page Builder – Qards, Philip M. Hofer (Frumph) PHPFreeChat, Arun Basil Lal Custom Login Admin Front-end CSS, Team Agence-Press CSS Adder By Agence-Press, Unihost Confirm Data, deano1987 AMP Toolbox amp-toolbox, Arun Basil Lal Admin CSS MU.This issue affects Montonio for WooCommerce: from n/a through 6.0.1; Wpopal Core Features: from n/a through 1.5.8; ArcStone: from n/a through 4.6.6; WooVirtualWallet – A virtual wallet for WooCommerce: from n/a through 2.2.1; WooVIP – Membership plugin for WordPress and WooCommerce: from n/a through 1.4.4; WooSupply – Suppliers, Supply Orders and Stock Management: from n/a through 1.2.2; Theme Minifier: from n/a through 2.0; Styles: from n/a through 1.2.3; WordPress Page Builder – Qards: from n/a through 1.0.5; PHPFreeChat: from n/a through 0.2.8; Custom Login Admin Front-end CSS: from n/a through 1.4.1; CSS Adder By Agence-Press: from n/a through 1.5.0; Confirm Data: from n/a through 1.0.7; AMP Toolbox: from n/a through 2.1.1; Admin CSS MU: from n/a through 2.6.

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

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

It affects 15 products.


Products: Agence-Press Css Adder, Arcstone Amo for Wp - Membership Management, Deano Amp Toolbox, Designmodo Qards, Frumph Phpfreechat, Longwatchstudio Woosupply, Longwatchstudio Woovip, Longwatchstudio Woovirtualwallet, Millionclues Admin Css Mu, Millionclues Custom Login Admin Front-End Css, Montonio Montonio for Woocommerce, Paulclark Styles, Squidesma Theme Minifier, Unihost Confirm Data, Wpopal Wpopal Core Features.

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

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

## Is CVE-2022-40700 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-40700 is a high-severity server-side request forgery vulnerability in AMO for WP – Membership Management AMP Toolbox, published on 19 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-40700 in the wild and no public exploit code.

Affected product: AMO for WP – Membership Management AMP Toolbox. 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-40700/ (Markdown: https://insights.sbomify.com/CVE-2022-40700/index.md)
```

## Sources

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

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