Safeguard
Vulnerability Analysis•

CVE-2022-3604: High CSV Injection in Contact Form Entries

CVE-2022-3604 is a CSV injection flaw in the Contact Form Entries WordPress plugin, rated high by NVD at 7.8. Update to version 1.3.0 or later.

Safeguard Security Team
3 min read

CVE-2022-3604 is a CSV injection flaw in the Contact Form Entries WordPress plugin before 1.3.0. NVD scores it 7.8 High, while WPScan scores it 4.7 Medium. Form data is written to an exported CSV without neutralisation, so update to version 1.3.0 or later.

What's affected

The record says the Contact Form Entries plugin before 1.3.0 does not validate data when it is output in a CSV file, which could lead to CSV injection. The vector is CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H: a local attack that needs a person to open the file.

WPScan's entry, published 2022-10-21, lists the plugin as contact-form-entries and the fix as 1.3.0, matching the record. It says the plugin stores entries from forms built with several popular form plugins.

The sources disagree on severity. NVD gives 7.8 High from the vector. WPScan gives 4.7 Medium. The difference is how much weight each gives to the need for a person to open the exported file in a spreadsheet and approve what happens next. I would plan the update for the next maintenance window at least, and sooner if staff regularly export entries.

Weakness class: CWE-1236.

How to check if you're exposed

With WP-CLI:

wp plugin get contact-form-entries --field=version

Or read the version on the Plugins page of the admin area. Anything before 1.3.0 is in range. Check deactivated plugins too, because their files remain on disk and some flaws can be reached without the plugin being active.

What to do now

  1. Find the sites that use the plugin.
  2. Update to 1.3.0 or later.
  3. Tell staff who export entries to open the files in a text editor or a spreadsheet with formula execution and external content turned off.
  4. Review existing stored entries for fields that begin with an equals sign, plus, minus or at sign.
  5. Delete the plugin if nobody uses the exported data.

Why it matters

CSV injection moves the danger from the website to the person who reads the data. A visitor submits a form with a value that looks like a spreadsheet formula. The plugin stores it, and later writes it into the export unchanged. When an employee opens the file, spreadsheet software may treat the value as a formula. The record files it as CWE-1236, improper neutralisation of formula elements in a CSV file.

The attacker does not need an account. A public contact form is enough, so the weak point is the whole path from a public input to a staff member's spreadsheet.

The common fix is to prefix risky leading characters with an apostrophe or a space on export, so the value is read as text. Any feature that exports user input to CSV should do it.

This CVE is not listed in the CISA Known Exploited Vulnerabilities catalog, and none of the pages I read state that it is exploited in the wild. That is a statement about what is known, not a reason to delay the fix.

Quick check

Does the attacker need an account on my site?

Not according to the record, which describes data from form submissions. A person must still open the exported file.

Why do the scores differ?

NVD scores 7.8 High and WPScan scores 4.7 Medium for the same issue. Both list 1.3.0 as the fix.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.