# CVE-2024-5503: WP Blog Post Layouts <= 1.1.3 - Authenticated (Contributor+) Local File Inlcusion

> Authenticated contributors can exploit a local file inclusion vulnerability in the WP Blog Post Layouts plugin to execute arbitrary PHP code on the server.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/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:** 21 Jun 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-rpr4-fpwh-9vfr

## What is CVE-2024-5503?

CVE-2024-5503 is a high-severity path traversal vulnerability in codevibrant WP Blog Post Layouts, published on 21 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Blog Post Layouts plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.1.3. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary PHP files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

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

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

It affects 1 product.


Products: Codevibrant Wp Blog Post Layouts.

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

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

## Is CVE-2024-5503 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-5503 is a high-severity path traversal vulnerability in codevibrant WP Blog Post Layouts, published on 21 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-5503 in the wild and no public exploit code.

Affected product: codevibrant WP Blog Post Layouts. 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-5503/ (Markdown: https://insights.sbomify.com/CVE-2024-5503/index.md)
```

## Sources

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

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