Convertkit Email Marketing\, Email Newsletter And Landing PagesWordPress extension · Convertkit
CVE-2024-31245
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 · uneditedInsertion of Sensitive Information into Log File vulnerability in ConvertKit.This issue affects ConvertKit: from n/a through 2.4.5.
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 confidenceThe ConvertKit WordPress plugin (versions through 2.4.5) has a log file information disclosure vulnerability where sensitive information is being written to log files. The CVSS 7.5 score indicates that logged data could include authentication tokens, API keys, user credentials, or PII that could be leveraged by attackers with log file access.
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
Convertkit Email Marketing\, Email Newsletter And Landing PagesWordPress extension
< 2.4.6CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 ConvertKit plugin versionNavigate to Plugins > Installed Plugins in WordPress admin, locate the ConvertKit plugin, and note the version number displayedAffected if The installed version is lower than 2.4.6 (e.g., 2.4.5 or earlier)
-
Check if plugin logging is enabledGo to ConvertKit plugin settings in WordPress admin panel. Look for a logging or debug setting, typically found under the plugin's advanced or debugging optionsAffected if Logging or debug mode is turned ON and the plugin version is below 2.4.6
-
Locate plugin log filesAccess your WordPress site via FTP or file manager. Check the wp-content/plugins/convertkit/ directory for files with .log extension or files named debug.log, convertkit.log, or similarAffected if Log files exist in the plugin directory and the plugin version is below 2.4.6
-
Inspect log contents for sensitive dataOpen any found log files and search for patterns such as 'api_key', 'token', 'password', 'secret', 'Authorization:', or email addresses that may indicate PII leakageAffected if Log files contain authentication tokens, API keys, credentials, or personally identifiable information
You are affected if the ConvertKit plugin version is below 2.4.6 AND logging is enabled, resulting in sensitive data being written to accessible log files.
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.
dbcve · scoped2.4.6
Upgrade ConvertKit to the latest version which should remove or properly sanitize sensitive data from log output. If upgrade is not immediately possible, review and restrict access to plugin log files, and audit logging statements to identify what data is being written.
ConvertKit Email Marketing plugin version 2.4.6
- Backup your WordPress site and database before proceeding with any updates
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate the ConvertKit Email Marketing plugin
- Check if current version is below 2.4.6
- If vulnerable, click 'Update Now' to upgrade to version 2.4.6
- After update, verify the new version number reflects 2.4.6
- Test that the ConvertKit functionality (email marketing, newsletters, landing pages) continues to work correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Convertkit Email Marketing\, Email Newsletter And Landing Pages
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-31245 — 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-31245 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