dbcve.org
Admin Css MuWordPress extension · Millionclues

CVE-2022-40700

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-19
Fix available
A fix is available. Upgrade to after 6.0.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a critical Server-Side Request Forgery (SSRF) vulnerability affecting 14 different WordPress plugins and themes. The vulnerability allows attackers to make the server perform arbitrary requests, potentially accessing internal services, cloud metadata endpoints, or performing port scans of internal infrastructure. The issue stems from insufficient validation of URLs or user-controlled request targets in the affected plugins.

MitigationUpdate all affected plugins to their latest versions, as patches are available for most listed versions. If patches are unavailable, implement network-level filtering to restrict outgoing requests from the web server and disable unnecessary URL-fetching functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Admin Css MuWordPress extension
Affected:<= 2.6
Amp ToolboxWordPress extension
Affected:<= 2.1.1
Confirm DataWordPress extension
Affected:<= 1.0.7
Css AdderWordPress extension
Affected:<= 1.5.0
Custom Login Admin Front End CssWordPress extension
Affected:<= 1.4.1
Montonio For WoocommerceWordPress extension
Affected:<= 6.0.1
PhpfreechatWordPress extension
Affected:<= 0.2.8
QardsWordPress extension
Affected:<= 1.0.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. List installed WordPress plugins
    Access the WordPress admin dashboard under Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory via file system or FTP/SSH to enumerate all installed plugins and their versions
    Affected if Any of the following plugins are installed: Millionclues Admin Css Mu, Deano Amp Toolbox, Unihost Confirm Data, Agence Press Css Adder, Millionclues Custom Login Admin Front End Css, Montonio Montonio For Woocommerce, Frumph Phpfreechat, or Designmodo Qards
  2. Compare installed version against affected ranges
    For each identified affected plugin, locate its version number in the plugin header (typically in the main PHP file or readme.txt) and compare against: Millionclues Admin Css Mu <= 2.6, Deano Amp Toolbox <= 2.1.1, Unihost Confirm Data <= 1.0.7, Agence Press Css Adder <= 1.5.0, Millionclues Custom Login Admin Front End Css <= 1.4.1, Montonio Montonio For Woocommerce <= 6.0.1, Frumph Phpfreechat <= 0.2.8, Designmodo Qards <= 1.0.5
    Affected if The installed version is equal to or lower than the listed version for any affected plugin
  3. Identify if plugin URL-fetching functionality is accessible
    Locate the plugin settings or features that accept URLs as input (commonly found in plugin admin panels, widget settings, or shortcode attributes that accept URLs for external resources, CSS imports, or API calls)
    Affected if The plugin exposes any setting or functionality that accepts user-supplied URLs, as this is the attack vector for SSRF exploitation
  4. Verify external request capability is enabled
    Check if the plugin functionality that allows server-side URL requests is active and not disabled via configuration, firewall, or web application firewall rules
    Affected if The plugin URL-fetching feature remains enabled and accessible to users (authenticated or unauthenticated depending on plugin access controls)
  5. Review server outgoing request logs
    Inspect web server access logs and WordPress debug logs for suspicious outbound requests originating from the server to internal IPs (127.0.0.1, 10.x.x.x, 192.168.x.x), cloud metadata endpoints (169.254.169.254), or unusual external domains
    Affected if Outbound requests are observed from the web server to internal network addresses or unexpected external destinations that were not initiated by legitimate admin actions

Your environment is affected if any of the eight listed WordPress plugins are installed at a version at or below the specified threshold and the plugin URL-fetching functionality is accessible and enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 6.0.1
Interim mitigation

Update all affected plugins to their latest versions, as patches are available for most listed versions. If patches are unavailable, implement network-level filtering to restrict outgoing requests from the web server and disable unnecessary URL-fetching functionality.

Fix this in Admin Css Mu Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-40700 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-40700 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data