Wordpress Comments Import And ExportWordPress extension · Webtoffee
CVE-2022-45370
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 WebToffee WordPress Comments Import & Export.This issue affects WordPress Comments Import & Export: from n/a through 2.3.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 confidenceThis is a CSV formula injection vulnerability in the WebToffee WordPress Comments Import & Export plugin. The plugin fails to properly neutralize formula elements (such as =, +, -, @, tab, CR/LF characters) when exporting comments to CSV format. When users open the exported CSV file in spreadsheet software like Excel or LibreOffice Calc, maliciously crafted formula characters can trigger code execution or data exfiltration attacks.
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
Wordpress Comments Import And ExportWordPress extension
<= 2.3.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 the plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and locate 'WebToffee Wordpress Comments Import And Export'. Note the version number displayed.Affected if The plugin version is 2.3.1 or lower
-
Confirm the vulnerable version rangeCompare the installed version number against the affected range: version 2.3.1 or earlier.Affected if Installed version is <= 2.3.1
-
Check if CSV export has been usedReview WordPress access logs or the plugin's export history for any CSV export operations performed using this plugin.Affected if CSV exports have been generated using the vulnerable plugin version
-
Inspect exported CSV files for formula charactersOpen any previously exported CSV files in a text editor and search for unescaped characters at the start of fields: =, +, -, @, or whitespace characters (tab, CR/LF). In a properly sanitized CSV, these should be preceded by a single quote (') or otherwise escaped.Affected if Any exported CSV contains formula-triggering characters (=, +, -, @, tab, CR/LF) at the beginning of field values without proper escaping
A user is affected if the WebToffee Comments Import & Export plugin version is 2.3.1 or lower AND CSV export functionality has been used, with the resulting files containing unescaped formula characters.
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 WebToffee WordPress Comments Import & Export plugin to the latest version which implements proper CSV formula character escaping/sanitization. Until patched, advise users to open exported CSV files only in text editors rather than spreadsheet applications.
Fix this in Wordpress Comments Import And Export
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-2022-45370 — 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-45370 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