# CVE-2024-52498: WordPress SP Blog Designer plugin <= 1.0.0 - Local File Inclusion vulnerability

> An attacker can exploit a path traversal flaw in the SP Blog Designer plugin to perform local file inclusion and read sensitive files.

- **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-3g56-vx8v-f22v

## What is CVE-2024-52498?

CVE-2024-52498 is a high-severity path traversal vulnerability in softpulseinfotech SP Blog Designer, published on 28 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Path Traversal: '.../...//' vulnerability in softpulseinfotech SP Blog Designer sp-blog-designer allows PHP Local File Inclusion.This issue affects SP Blog Designer: from n/a through <= 1.0.0.

Weakness: CWE-35 (Path Traversal: '.../...//')

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


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

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

## Is CVE-2024-52498 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-52498 is a high-severity path traversal vulnerability in softpulseinfotech SP Blog Designer, 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-52498 in the wild and no public exploit code.

Affected product: softpulseinfotech SP Blog Designer. 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-52498/ (Markdown: https://insights.sbomify.com/CVE-2024-52498/index.md)
```

## Sources

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

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