dbcve.org
Icegram ExpressWordPress extension · Icegram

CVE-2022-45810

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-07
Fix available
A fix is available. Upgrade to after 5.5.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper Neutralization of Formula Elements in a CSV File vulnerability in Icegram Icegram Express – Email Marketing, Newsletters and Automation for WordPress & WooCommerce.This issue affects Icegram Express – Email Marketing, Newsletters and Automation for WordPress & WooCommerce: from n/a through 5.5.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 · high confidence

The Icegram Express WordPress plugin fails to sanitize formula elements (=, +, -, @, etc.) in CSV exports, allowing attackers to inject malicious spreadsheet formulas. When users open the exported CSV in Excel or other spreadsheet software, the formulas can execute arbitrary commands on the victim's machine.

MitigationUpdate Icegram Express to the latest version (5.5.3 or later). If immediate update is not feasible, disable CSV export functionality or implement server-side sanitization to neutralize formula characters in exported data fields.

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
Icegram ExpressWordPress extension
Affected:<= 5.5.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Icegram Express plugin is installed
    Check if the Icegram Express plugin exists in your WordPress installation under wp-content/plugins/icegram-express/ or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if Icegram Express plugin is present in the WordPress installation
  2. Determine installed plugin version
    Access the plugin details page in WordPress admin (Plugins > Installed Plugins > Icegram Express) or inspect the plugin header in wp-content/plugins/icegram-express/icegram-express.php for the 'Version' field
    Affected if The displayed version is 5.5.2 or lower
  3. Identify CSV export usage
    Check if the CSV export feature is being used by reviewing the plugin settings for any export functionality (typically under Icegram Express menu > Subscribers > Export or similar export options)
    Affected if CSV export functionality is enabled or has been used to generate subscriber or campaign exports
  4. Inspect recent CSV exports for formula characters
    Locate any recently exported CSV files in the wp-content/uploads/ directory or check downloaded export files for the presence of formula characters at the start of fields: =, +, -, @, tab (0x09), or carriage return (0x0D)
    Affected if Exported CSV files contain data fields starting with =, +, -, @, or other formula-initiating characters

You are affected if Icegram Express version 5.5.2 or lower is installed and CSV export functionality is being used to generate exports containing unsanitized formula characters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 5.5.2
Interim mitigation

Update Icegram Express to the latest version (5.5.3 or later). If immediate update is not feasible, disable CSV export functionality or implement server-side sanitization to neutralize formula characters in exported data fields.

Recommended fix Moderate confidence

5.5.3 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Icegram Express plugin
  4. Click 'Update Now' if an update is available, or manually update to version 5.5.3 or later
  5. Verify the update completed successfully

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Icegram Express Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45810 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-45810 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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