MailrelayWordPress extension
CVE-2023-45108
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Mailrelay plugin <= 2.1.1 versions.
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the Mailrelay plugin version 2.1.1 and earlier. This allows attackers to trick authenticated users into performing unintended actions (such as modifying plugin settings or sending emails through the plugin) by leveraging the lack of anti-CSRF token validation on state-changing operations.
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
MailrelayWordPress extension
<= 2.1.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Mailrelay plugin is installedNavigate to the WordPress admin dashboard and check the installed plugins list, or inspect the wp-content/plugins directory for the mailrelay folderAffected if The Mailrelay plugin appears in the installed plugins list
-
Check the installed Mailrelay plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find the Mailrelay plugin version number, or read the main plugin file header for the Version fieldAffected if The installed version is 2.1.1 or any version lower than 2.1.1
-
Identify state-changing admin actionsReview the Mailrelay plugin admin pages for any forms that modify settings, send test emails, or interact with the Mailrelay API. Check if these forms include nonce tokens in their submissionsAffected if The plugin has admin forms or actions that lack anti-CSRF nonce token validation in their handling code
-
Verify authenticated user exposureConfirm that administrative users with access to the Mailrelay plugin settings perform actions that could be triggered via CSRF (such as saving configuration or triggering email sends)Affected if Authenticated administrators use the Mailrelay plugin to modify settings or send emails
A user is affected if the Mailrelay plugin version is 2.1.1 or earlier and administrators use the plugin's state-changing features (settings modifications, email sending) without CSRF protection in place
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to the latest patched version of the Mailrelay plugin. Additionally, implement anti-CSRF nonce tokens on all form submissions and state-changing admin actions to prevent unauthorized requests.
Fix this in Mailrelay
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45108 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-45108 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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