CVE-2019-20180

TablePress <= 1.14 - Authenticated (Author+) CSV Injection

2020-02-01 00:00
0xPablito

Strategic Overview

Status
Patched in 2.0
Affected Version
<= 1.14
CVSS
8.0High
Weakness type
CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
CVE
CVE-2019-20180
View all TablePress – Tables in WordPress made easy vulnerabilities

At a glance

CVE-2019-20180 is a high-severity Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in the TablePress WordPress plugin, affecting versions <= 1.14. It carries a CVSS score of 8.0 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 2.0; sites on affected versions should update now. Disclosed February 2020, reported by 0xPablito.

Vulnerability Overview

The TablePress plugin for WordPress is vulnerable to CSV Injection in versions up to and including 1.14 via the tablepress[data] value. This makes it possible for attackers with author level access 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. This vulnerability is not likely to be exploited in the wild due to its high complexity and many modern day protections, however, it could have a significant impact if exploited successfully at it's worst impact. Please note that while the CVE record says this issue was patched in 1.10, our team confirmed it was still exploitable in 1.14. The has been patched in version 2.0 of TablePress.

Technical Analysis

The vector marks this flaw as remotely reachable over the network. 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 2.0, or a newer patched version

How does WordSec protect against this?

An attacker needs Author access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: TablePress 2.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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