Commenter EmailsWordPress extension · Coffee2code
CVE-2022-45360
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 · uneditedImproper Neutralization of Formula Elements in a CSV File vulnerability in Scott Reilly Commenter Emails.This issue affects Commenter Emails: from n/a through 2.6.1.
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 confidenceImproper Neutralization of Formula Elements in a CSV File vulnerability in the Commenter Emails WordPress plugin allows attackers to inject spreadsheet formula characters (e.g., =, +, -, @) into email address or name fields. When administrators export commenter data to CSV and open it in spreadsheet software, the injected formulas are executed, potentially leading to arbitrary command execution on the victim's machine.
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
Commenter EmailsWordPress extension
<= 2.6.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
- 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.
-
Verify plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and locate 'Coffee2code Commenter Emails'. Check the version number displayed under the plugin name. Alternatively, check the plugin header in wp-content/plugins/commenter-emails/commenter-emails.php for the 'Version' tag.Affected if The installed version is 2.6.1 or lower (any version up to and including 2.6.1).
-
Confirm CSV export feature existsAccess the WordPress admin and look for the comment export functionality provided by this plugin. Typically found in Comments > Export Comments or a similar admin page. Check if the plugin offers a 'Export to CSV' or similar button in the comments admin area.Affected if The plugin provides CSV export functionality for commenter data and the version is vulnerable.
-
Test CSV export output for formula charactersAdd a test comment with an email address prefixed with formula characters (e.g., [email protected] or [email protected]). Export comments using the plugin's CSV export feature. Open the resulting CSV file in a text editor and examine the raw output for the email field.Affected if The exported CSV contains unescaped formula characters (=, +, -, @) at the start of the email or name fields without proper escaping (such as prefixing with a single quote or apostrophe).
A user is affected if the Coffee2code Commenter Emails plugin version is 2.6.1 or lower and the CSV export feature is used to export commenter data containing injected formula characters in email or name fields.
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 Commenter Emails to the latest version which should contain proper sanitization of formula characters in CSV exports, or implement output encoding to escape special CSV formula characters (=, +, -, @, tab, CR, LF) when generating CSV files.
Fix this in Commenter Emails
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45360 — 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-2022-45360 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