TablePress – Tables in WordPress made easy <= 2.3 - Authenticated (Author+) Server-Side Request Forgery via DNS Rebind
Strategic Overview
- Status
- Patched in 2.3.2
- Affected Plugin
- TablePress – Tables in WordPress made easy
- Affected Version
<= 2.3.1- CVSS
- 6.4Medium
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2024-4354
At a glance
CVE-2024-4354 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the TablePress WordPress plugin, affecting versions <= 2.3.1. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 2.3.2; sites on affected versions should update now. Disclosed June 2024, reported by Tobias Weißhaar (kun_19).
Vulnerability Overview
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.
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.
CWE-918: Server-Side Request Forgery (SSRF)
TablePress <= 2.3.1 carries this weakness at get_files_to_import(), and reaching it takes an account at Author level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For TablePress the fix is 2.3.2: builds <= 2.3.1 are affected, anything from 2.3.2 onward is not.
Remediation
Update to version 2.3.2, 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.3.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in TablePress – Tables in WordPress made easy
- 8.0CVE-2019-20180: TablePress <= 1.14 CSV Injection
CVE-2019-20180 - 7.5CVE-2024-45293: PHPSpreadsheet Library < 2.3.0 XXE Injection
CVE-2024-45293 - 6.4CVE-2025-12324: TablePress – Tables in WordPress made easy Stored XSS
CVE-2025-12324 - 6.4CVE-2025-9500: TablePress <= 3.2 Stored Cross-Site Scripting
CVE-2025-9500 - 6.4CVE-2025-5096: TablePress <= 3.1.2 DOM-Based Stored XSS
CVE-2025-5096 - 6.4CVE-2025-2685: TablePress – Tables in WordPress made easy Stored XSS
CVE-2025-2685 - 6.4CVE-2024-9595: TablePress <= 2.4.2 Stored Cross-Site Scripting
CVE-2024-9595 - 6.1CVE-2026-56051: TablePress Reflected XSS
CVE-2026-56051
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C