Security readout for executives and security teams
Plain-English summary
CVE-2022-40700 is a high-severity SSRF issue spanning multiple WordPress plugins. A vulnerable site could be abused to make its server send unintended requests, potentially exposing sensitive internal data. The source bundle does not provide evidence of active exploitation, but the remote, unauthenticated nature makes exposed WordPress sites worth prioritizing.
Executive priority
Treat as high priority for WordPress estates, especially revenue-generating WooCommerce sites. Prioritize inventory first, then update, disable, or isolate affected plugins based on vendor guidance and business need.
Technical view
The CVE describes CWE-918 server-side request forgery across 15 WordPress plugins, including WooCommerce, membership, admin CSS, page builder, chat, and AMP-related plugins. CVSS 3.1 is 8.2 with network access, low complexity, no privileges, and no user interaction. Reported impact is high confidentiality and low integrity.
Likely exposure
Exposure is most likely on public WordPress or WooCommerce sites running one of the named plugin slugs at or below the affected versions. Sites with internal network access, cloud metadata reachability, or weak outbound filtering may face higher business risk.
Exploitation context
The bundle marks KEV as false and provides no cited evidence of active exploitation. The CVSS vector indicates unauthenticated remote reachability and low attack complexity. Evidence is incomplete on exploit maturity, patch availability, and whether each plugin is still maintained.
Researcher notes
The bundle identifies broad plugin coverage but does not include endpoint details, proof-of-concept status, or confirmed fixes. Avoid assuming one uniform remediation path across all plugins. Validation should focus on installed slug/version matching and SSRF exposure controls.
Mitigation direction
- Inventory WordPress plugin slugs and versions across all sites.
- Check CVE and Patchstack entries for vendor-specific fixed versions or guidance.
- Update affected plugins when an official fixed release is available.
- Disable or remove affected plugins when no maintained fix is available.
- Restrict outbound requests from web servers to required destinations only.
- Review WAF or hosting controls for SSRF protections.
Validation and detection
- Compare installed plugin slugs against the affected package list.
- Verify installed versions are above the affected ranges where fixed versions exist.
- Check server logs for unusual outbound requests from WordPress processes.
- Confirm web tier cannot reach cloud metadata or internal-only services.
- Document exceptions for plugins without clear vendor remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-40700 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N3.94.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/vulnerability/montonio-for-woocommerce/wordpress-montonio-for-woocommerce-plugin-6-0-1-server-side-request-forgery-ssrf?_s_id=cveCVE reference · vdb-entry
- https://patchstack.com/database/vulnerability/wpopal-core-features/wordpress-wpopal-core-features-plugin-1-5-7-server-side-request-forgery-ssrf?_s_id=cveCVE reference · vdb-entry
- https://patchstack.com/database/vulnerability/wp-amo/wordpress-amo-for-wp-plugin-4-6-6-server-side-request-forgery-ssrf?_s_id=cveCVE reference · vdb-entry
- https://patchstack.com/database/vulnerability/woovirtualwallet/wordpress-woovirtualwallet-plugin-2-2-1-server-side-request-forgery-ssrf?_s_id=cveCVE reference · vdb-entry
- https://patchstack.com/database/vulnerability/woovip/wordpress-woovip-plugin-1-4-4-server-side-request-forgery-ssrf?_s_id=cveCVE reference · vdb-entry
- https://patchstack.com/database/vulnerability/woosupply/wordpress-woosupply-plugin-1-2-2-server-side-request-forgery-ssrf?_s_id=cveCVE reference · vdb-entry
- https://patchstack.com/database/vulnerability/theme-minifier/wordpress-theme-minifier-plugin-2-0-server-side-request-forgery-ssrf?_s_id=cveCVE reference · vdb-entry
- https://patchstack.com/database/vulnerability/styles/wordpress-styles-plugin-1-2-3-server-side-request-forgery-ssrf?_s_id=cveCVE reference · vdb-entry
- https://patchstack.com/database/vulnerability/qards-free/wordpress-wordpress-page-builder-qards-plugin-1-0-5-server-side-request-forgery-ssrf?_s_id=cveCVE reference · vdb-entry
- https://patchstack.com/database/vulnerability/phpfreechat/wordpress-phpfreechat-plugin-0-2-8-server-side-request-forgery-ssrf?_s_id=cveCVE reference · vdb-entry
- https://patchstack.com/database/vulnerability/custom-login-admin-front-end-css-with-multisite-support/wordpress-custom-login-admin-front-end-css-plugin-1-4-1-server-side-request-forgery-ssrf?_s_id=cveCVE reference · vdb-entry
- https://patchstack.com/database/vulnerability/css-adder-by-agence-press/wordpress-css-adder-by-agene-press-plugin-1-5-0-server-side-request-forgery-ssrf?_s_id=cveCVE reference · vdb-entry
- https://patchstack.com/database/vulnerability/confirm-data/wordpress-confirm-data-plugin-1-0-7-unauth-server-side-request-forgery-ssrf-vulnerability?_s_id=cveCVE reference · vdb-entry
- https://patchstack.com/database/vulnerability/amp-toolbox/wordpress-amp-toolbox-plugin-2-1-1-server-side-request-forgery-ssrf?_s_id=cveCVE reference · vdb-entry
- https://patchstack.com/database/vulnerability/admin-css-mu/wordpress-admin-css-mu-plugin-2-6-server-side-request-forgery-ssrf-vulnerability?_s_id=cveCVE reference · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.