# CVE-2024-52497: WordPress Shopready plugin <= 3.6 - Local File Inclusion vulnerability

> An attacker can exploit a Local File Inclusion vulnerability in the Shopready WordPress plugin to read arbitrary files or execute code.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 28 Nov 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-4rwc-5m33-7fpv

## What is CVE-2024-52497?

CVE-2024-52497 is a high-severity path traversal vulnerability in quomodosoft Shopready, published on 28 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in quomodosoft Shopready shopready-elementor-addon allows PHP Local File Inclusion.This issue affects Shopready: from n/a through <= 3.6.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

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


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

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

## Is CVE-2024-52497 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-52497 is a high-severity path traversal vulnerability in quomodosoft Shopready, published on 28 Nov 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-52497 in the wild and no public exploit code.

Affected product: quomodosoft Shopready. 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-52497/ (Markdown: https://insights.sbomify.com/CVE-2024-52497/index.md)
```

## Sources

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

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