# CVE-2024-4354: TablePress – Tables in WordPress made easy <= 2.3 - Authenticated (Author+) Server-Side Request Forgery via DNS Rebind

> Authenticated authors can exploit SSRF via DNS rebinding to access internal services, mitigated by restricting import features to administrators.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-8q72-v33x-gggr

## What is CVE-2024-4354?

CVE-2024-4354 is a medium-severity server-side request forgery vulnerability in tobiasbg TablePress – Tables in WordPress made easy, published on 7 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2024-4354?

It affects 1 product.


Products: Tablepress Tablepress.

## How do I fix CVE-2024-4354?

No fix has been published for CVE-2024-4354 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-4354 being exploited?

There is no known exploitation of CVE-2024-4354 in the wild and no public exploit code.

## Other vulnerabilities in tobiasbg TablePress – Tables in WordPress made easy

- [CVE-2019-20180](https://insights.sbomify.com/CVE-2019-20180/): Other in n/a (medium 6.8)
- [CVE-2025-5096](https://insights.sbomify.com/CVE-2025-5096/): TablePress <= 3.1.2 - Authenticated (Contributor+) DOM-Based Stored Cross-Site Scripting via Multiple Parameters (medium 6.4)
- [CVE-2025-2685](https://insights.sbomify.com/CVE-2025-2685/): TablePress – Tables in WordPress made easy <= 3.0.4 - Authenticated (Author+) Stored Cross-Site Scripting (medium 6.4)
- [CVE-2024-9595](https://insights.sbomify.com/CVE-2024-9595/): TablePress <= 2.4.2 - Authenticated (Author+) Stored Cross-Site Scripting (medium 6.4)
- [CVE-2017-10889](https://insights.sbomify.com/CVE-2017-10889/): XML external entity in TablePress (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4354 and fix it if it is affected.

What it is: CVE-2024-4354 is a medium-severity server-side request forgery vulnerability in tobiasbg TablePress – Tables in WordPress made easy, published on 7 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-4354 in the wild and no public exploit code.

Affected product: tobiasbg TablePress – Tables in WordPress made easy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-4354/ (Markdown: https://insights.sbomify.com/CVE-2024-4354/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-4354
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-4354
- OSV: https://osv.dev/vulnerability/CVE-2024-4354

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-4354/
Summaries are generated and may contain mistakes; the official description above is the record.