WordPress security changelog
MEDIUM CVE-2024-4354 Modified

TablePress – Tables in WordPress made easy: Server-side request forgery

TablePress – Tables in WordPress made easy is affected by server-side request forgery. Exploitation requires at least author-level access. The vulnerable server can be induced to make attacker-selected network requests.

CVE / CNA score 6.4 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
TablePress – Tables in WordPress made easy
Plugin slug
tablepress
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Jun 07, 2024
Weakness
CWE-918 — Server-Side Request Forgery (SSRF)

This CVE was published Jun 07, 2024 and is one of 10 known issues for this plugin.

Update, patch or deactivate.

Update TablePress – Tables in WordPress made easy to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

The TablePress – Tables in WordPress made easy plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.3 via the get_files_to_import() function. This makes it possible for authenticated attackers, with author-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. Due to the complex nature of protecting against DNS rebind attacks in WordPress software, we settled on the developer simply restricting the usage of the URL import functionality to just administrators. While this is not optimal, we feel this poses a minimal risk to most site owners and ideally WordPress core would correct this issue in wp_safe_remote_get() and other functions.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Primary and upstream sources