Contact Form 7 Campaign Monitor ExtensionWordPress extension · Renzojohnson
CVE-2024-44019
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 · uneditedMissing Authorization vulnerability in Renzo Johnson Contact Form 7 Campaign Monitor Extension contact-form-7-campaign-monitor-extension.This issue affects Contact Form 7 Campaign Monitor Extension: from n/a through <= 0.4.67.
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 confidenceMissing Authorization vulnerability in the Contact Form 7 Campaign Monitor Extension plugin allows unauthenticated or unauthorized users to access sensitive functionality or perform actions that should require higher privileges. The plugin fails to implement proper capability checks or authorization validation before executing sensitive 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
Contact Form 7 Campaign Monitor ExtensionWordPress extension
<= 0.4.67CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 plugin installationCheck your WordPress plugins directory for the 'contact-form-7-campaign-monitor-extension' folder, or list installed plugins via wp-admin > PluginsAffected if The plugin folder exists in wp-content/plugins/
-
Identify installed versionOpen the plugin's main PHP file (typically in the plugin root) and check the 'Version' header in the plugin comment block, or check the version listed in wp-admin > Plugins > Plugin DetailsAffected if Version number is 0.4.67 or lower (any version <= 0.4.67)
-
Check for active Campaign Monitor integrationNavigate to the plugin settings in WordPress admin (usually under Contact > Campaign Monitor or plugin-specific settings) and check if Campaign Monitor API credentials are configured and the integration is enabledAffected if Campaign Monitor API key/credentials are saved and the integration toggle is enabled or active
-
Verify authorization on integration endpointsTest access to Campaign Monitor integration URLs (typically forms submitting to the plugin's AJAX handlers or direct API endpoints) without authentication using a browser or HTTP tool to see if requests are processed without loginAffected if HTTP requests to integration endpoints return successful responses without requiring WordPress authentication
You are affected if the plugin is installed, the version is 0.4.67 or lower, and Campaign Monitor integration features are enabled and accessible without proper authorization checks.
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 the plugin to the latest version once available, or disable and remove the plugin until a patched version can be deployed. If immediate patching is not possible, restrict access to the affected endpoints at the web server level.
Fix this in Contact Form 7 Campaign Monitor Extension
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-44019 — 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-44019 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