Security readout for executives and security teams
Plain-English summary
This WordPress plugin flaw lets an already high-privileged user abuse insufficient AJAX authorization to make the server send blind requests. The practical risk is highest on multisite WordPress environments where site administrators are not fully trusted. The bundle does not show active exploitation.
Executive priority
Treat this as a high-priority hygiene fix for WordPress multisite or shared-admin environments. It is not shown as actively exploited, but SSRF can expose sensitive internal services if the server has broad network reach.
Technical view
CVE-2022-2352 is a CWE-918 blind SSRF issue in Post SMTP Mailer/Email Log before 2.1.7. Some AJAX actions lack proper authorization, enabling high-privilege users such as admins to trigger server-side requests. CVSS 3.1 is 7.2 with PR:H and no user interaction.
Likely exposure
Exposure is likely limited to WordPress sites running Post SMTP Mailer/Email Log before 2.1.7. Multisite deployments with delegated or semi-trusted administrators are the main concern. Single-site environments with tightly trusted admins have lower practical exposure, but should still update.
Exploitation context
The source bundle and KEV status do not confirm active exploitation. The vulnerability requires high privileges, but SSRF can matter because the WordPress server may reach internal services, metadata endpoints, or restricted network locations unavailable to the user directly.
Researcher notes
Evidence is limited to the CVE description and WPScan reference. The bundle does not name specific AJAX action identifiers, proof-of-concept details, or observed exploitation. Validate exposure by version and deployment model rather than assuming internet-wide exploitability.
Mitigation direction
- Update Post SMTP Mailer/Email Log to 2.1.7 or later.
- Review vendor guidance for any additional recommended remediation.
- Limit WordPress administrator access to trusted users only.
- Restrict server egress to internal or sensitive network destinations where feasible.
- Prioritize multisite environments with delegated admin roles.
Validation and detection
- Inventory WordPress sites using Post SMTP Mailer/Email Log.
- Confirm installed plugin versions are not older than 2.1.7.
- Identify whether affected sites run WordPress multisite.
- Review administrator accounts for unnecessary or shared access.
- Check logs for unusual admin AJAX activity or unexpected server-side requests.
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-2352 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
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/dc99ac40-646a-4f8e-b2b9-dc55d6d4c55cCVE reference · x_refsource_MISC
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.