CVE-2022-1202

WP-CRM – Customer Relations Management for WordPress <= 1.2.1 - CSV injection

2022-05-18 00:00
Ankur Bakre

Strategic Overview

Status
Unpatched
Affected Version
<= 1.2.1
CVSS
7.2High
Weakness type
CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
CVE
CVE-2022-1202
View all WP-CRM – Customer Relations Management for WordPress vulnerabilities

At a glance

CVE-2022-1202 is a high-severity Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in the WP-CRM WordPress plugin, affecting versions <= 1.2.1. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). No fixed release has been reported yet; treat installations running this software as exposed. Disclosed May 2022, reported by Ankur Bakre.

Vulnerability Overview

The WP-CRM WordPress plugin through 1.2.1 does not validate and sanitise fields when exporting people to a CSV file, leading to a CSV injection vulnerability.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP-CRM: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Firewall
  • Alerts

External References

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C