Post SMTP Mailer/Email Log: Server-Side Request Forgery
CVE-2022-2352 is a high-severity server-side request forgery vulnerability in Post SMTP Mailer/Email Log, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. The record lists version 2.1.7 as the first without the flaw, so updating Post SMTP Mailer/Email Log to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.38% chance of exploitation within 30 days, higher than 73% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Post SMTP Mailer/Email Log to 2.1.7 or a later version.
- Update Post Smtp to 2.1.7 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Post SMTP Mailer/Email Log | Post SMTP Mailer/Email Log | 2.1.7 up to, but not including, 2.1.7 | 2.1.7 |
| Wpexperts | Post Smtp | before 2.1.7 | 2.1.7 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.2 | High | NVD |
| CVSS 3.1 | 7.2 | High | CISA (ADP) |
Official description
The Post SMTP Mailer/Email Log WordPress plugin before 2.1.7 does not have proper authorisation in some AJAX actions, which could allow high privilege users such as admin to perform blind SSRF on multisite installations for example.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Server-Side Request Forgery
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
How developers prevent this class of flaw
- If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
- If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- wpscan.com/vulnerability/dc99ac40-646a-4f8e-b2b9-dc55d6d4c55cExploit, Third Party Advisory
Recent Server-Side Request Forgery vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
- 8.8 High severity
- 8.4 High severity
- 8.8 High severity
Spotted an error? Tell us.