CVE-2022-40700 is a high severity (CVSS 8.2) server-side request forgery shared by 15 WordPress plugins, including Admin CSS MU, AMP Toolbox and Confirm Data. Patchstack lists a fix only for Admin CSS MU, version 2.7. For the others, update if a release exists or remove the plugin.
What's affected
One CVE identifier covers a batch of plugins from different authors. The record lists these products and the last affected version for each:
- Montonio for WooCommerce, through 6.0.1
- Wpopal Core Features, through 1.5.8
- AMO for WP Membership Management (ArcStone wp-amo), through 4.6.6
- WooVirtualWallet, through 2.2.1
- WooVIP Membership, through 1.4.4
- WooSupply, through 1.2.2
- Theme Minifier, through 2.0
- Styles, through 1.2.3
- WordPress Page Builder Qards, through 1.0.5
- PHPFreeChat, through 0.2.8
- Custom Login Admin Front-end CSS, through 1.4.1
- CSS Adder By Agence-Press, through 1.5.0
- Confirm Data, through 1.0.7
- AMP Toolbox, through 2.1.1
- Admin CSS MU, through 2.6
I read three of the Patchstack entries. Admin CSS MU is fixed in 2.7. The AMP Toolbox and Confirm Data entries say no official patch is available. I did not read the entries for the other twelve, so their fix status is unconfirmed. The record scores the CVE 8.2 (High) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N, and Patchstack gives the required privilege for the three entries I read as none or unauthenticated. The class is CWE-918 (Server-Side Request Forgery).
How to check if you're exposed
Start with an inventory. If you manage the site with WP-CLI, this lists every plugin with its version and whether an update is waiting:
wp plugin list --fields=name,status,version,update
Look for the folder admin-css-mu. That folder name comes from the Patchstack entry for this issue, so confirm it matches what sits under wp-content on your site. Without WP-CLI, open the Plugins screen in the dashboard and read the version shown under the name. Compare each installed plugin with the list above. Admin CSS MU 2.6 or lower is affected and 2.7 is patched. For every other name on the list, treat versions at or below the number shown as affected until you have confirmed a fix.
Check staging copies, old multisite subsites and inactive plugins too. A deactivated plugin is still on disk, and some of these bugs are reachable through files that load even when the plugin is switched off, so deactivation alone is not a fix. Delete what you do not use.
Several of these are must-use or small utility plugins that sit in wp-content/mu-plugins, which the normal plugin screen does not list under Plugins. Check that folder too:
ls wp-content/mu-plugins
What to do now
- List every plugin and must-use plugin on every site you run, and compare with the list above.
- Update Admin CSS MU to 2.7 or later.
- For AMP Toolbox and Confirm Data, where Patchstack lists no official patch, remove the plugin or replace it.
- For the other twelve, open each Patchstack entry or the plugin's page, and update if a fixed release exists. Remove the plugin if none does.
- If you cannot remove a plugin right away, block outbound requests from the web server to internal address ranges and cloud metadata addresses at the network layer.
- Review outbound connection logs from the web server for requests to internal hosts.
Why it matters
Server-side request forgery means the server can be made to send requests to a destination chosen by the caller. That is dangerous because the server sits inside your network and can reach services the outside world cannot: internal admin panels, databases with no login, and on cloud hosts the metadata service that hands out credentials. Patchstack describes it as letting attackers make the server connect to internal systems and leak data from behind the firewall.
The record's score reflects that: high confidentiality impact, low integrity impact, no privileges and no user interaction. Patchstack nevertheless rates its own priority for the Admin CSS MU entry as Low with no impactful threat, which is a reminder that the CVSS number and the real world risk on a given site can differ. A plugin that fetches a user supplied address is a classic place for this flaw, but the sources I read do not detail how each plugin does it, so I will not.
The wider lesson is about shared CVEs. One identifier across fifteen unrelated plugins is easy to miss in a scan that keys on a single product name. The record's KEV flag is false, and nothing I fetched reports exploitation in the wild.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Why does one CVE cover so many plugins?
The record lists many products with the same flaw class, and they share the one identifier. Each plugin has its own affected range and its own fix status.
Which of these have a patch?
From the entries I read, Admin CSS MU has one, in 2.7. AMP Toolbox and Confirm Data do not. The rest are unconfirmed.
Sources
- Patchstack entry for Admin CSS MU 2.6
- Patchstack entry for AMP Toolbox 2.1.1
- Patchstack entry for Confirm Data 1.0.7
Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.
Last reviewed: 19 October 2026.