Security readout for executives and security teams
Plain-English summary
This is a medium-severity CSRF issue in the WordPress Mailrelay plugin through version 2.1.1. An attacker may be able to trick a logged-in user into making an unintended plugin-related change. The provided sources do not identify the exact action affected, a patch version, or active exploitation.
Executive priority
Handle as a routine but time-bound WordPress plugin remediation item. There is no sourced evidence of active exploitation, but CSRF can affect site integrity if an administrator is tricked. Prioritize internet-facing business sites and sites with multiple administrators.
Technical view
CVE-2023-45108 is classified as CWE-352 Cross-Site Request Forgery with CVSS 3.1 score 4.3. The vector indicates network access, low complexity, no attacker privileges, required user interaction, unchanged scope, low integrity impact, and no confidentiality or availability impact. Affected metadata is sparse beyond Mailrelay plugin <= 2.1.1.
Likely exposure
Exposure is most likely limited to WordPress installations running the Mailrelay plugin at version 2.1.1 or earlier. The source bundle provides no CPEs and limited product metadata, so inventory validation should rely on installed WordPress plugin names and versions.
Exploitation context
The source bundle does not report active exploitation, and this CVE is not marked KEV. CSRF typically depends on a targeted authenticated user interacting with attacker-controlled content, but the provided sources do not specify the required role or impacted action.
Researcher notes
The public evidence is thin: it names CSRF in Mailrelay <= 2.1.1 and provides CVSS details, but does not describe the vulnerable endpoint, nonce failure, required role, exploit maturity, or fixed version. Avoid assuming impact beyond low integrity without additional vendor data.
Mitigation direction
- Inventory WordPress sites for the Mailrelay plugin.
- Flag installed Mailrelay versions 2.1.1 or earlier.
- Check Patchstack, vendor, or WordPress plugin guidance for fixed versions.
- Update, disable, or remove affected plugin installations per vendor guidance.
- Review administrative account activity for unexpected plugin configuration changes.
Validation and detection
- Confirm plugin slug or name matches Mailrelay.
- Record installed plugin version from WordPress administration or asset inventory.
- Verify whether version is 2.1.1 or earlier.
- Check whether the site still requires the plugin.
- Document remediation status and remaining exceptions.
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-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookupCVE-2023-45108 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
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
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.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.