WordCamp Talks < 1.0.0 Beta3 - CSV Injection

2017-10-23 00:00
White Hatter

Strategic Overview

Status
Patched in 1.0.0-beta3
Affected Plugin
wordcamp-talks
Affected Version
< 1.0.0-beta3
CVSS
8.0High
Weakness type
CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
CVE
CVE pending
View all wordcamp-talks vulnerabilities

At a glance

This record tracks a high-severity Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in the wordcamp-talks WordPress plugin, affecting versions < 1.0.0-beta3. It carries a CVSS score of 8.0 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 1.0.0-beta3; sites on affected versions should update now. Disclosed October 2017, reported by White Hatter.

Vulnerability Overview

The WordCamp Talks plugin for WordPress is vulnerable to CSV Injection in versions up to, and including, 1.0.0 Beta2 via the wct_generate_csv_content() function. This allows authenticated attackers, with contributor-level permissions and above, to embed untrusted input into exported CSV files, which can result in code execution when these files are downloaded and opened on a local system with a vulnerable configuration.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed. 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

Update to version 1.0.0-beta3, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to wordcamp-talks: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: wordcamp-talks 1.0.0-beta3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

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