Freshmail For WordpressWordPress extension · Borbis
CVE-2024-22304
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 Borbis Media FreshMail For WordPress.This issue affects FreshMail For WordPress: from n/a through 2.3.2.
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 FreshMail For WordPress plugin by Borbis Media allows attackers to trick authenticated users into performing unintended actions (such as modifying email subscription settings or subscriber data) by exploiting the lack of proper anti-CSRF tokens on state-changing requests.
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
Freshmail For WordpressWordPress extension
<= 2.3.2CVSS 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.
-
Verify FreshMail plugin is installedLog into WordPress admin dashboard, navigate to Plugins > Installed Plugins. Look for 'FreshMail' or 'FreshMail for WordPress' by Borbis Media in the plugin list.Affected if Plugin is not found in the installed plugins list - you are not affected.
-
Confirm plugin version numberIn the Plugins page, click on the plugin name or 'View Details' link for FreshMail. Note the version number displayed next to the plugin name.Affected if Version is 2.3.2 or lower - proceed to next check.
-
Check if plugin is activeOn the Plugins page, verify if FreshMail is activated (the plugin will show as 'Active' under the plugin name). CSRF only affects active plugins with enabled functionality.Affected if Plugin is not active - you are not affected by this CSRF vulnerability.
-
Identify state-changing features in useNavigate to the FreshMail plugin settings page (usually under Settings or a dedicated FreshMail menu). Look for forms that modify subscription settings, subscriber data, or email list configuration - these are the state-changing endpoints vulnerable to CSRF.Affected if Plugin has active subscription forms, subscriber management, or settings that can be modified - you are potentially affected if version is <= 2.3.2.
You are affected if FreshMail for WordPress plugin is active at version 2.3.2 or lower and has any subscription forms or subscriber management features in use.
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 FreshMail For WordPress to a patched version beyond 2.3.2 once released; implement SameSite cookies and nonce-based CSRF protection for all form submissions and AJAX actions in the plugin.
Fix this in Freshmail For Wordpress
Scoped from the published advisory
- Consultation1.0 h
- Implementation3.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 $1,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22304 — 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-2024-22304 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