# CVE-2024-5577: Where I Was, Where I Will Be <= 1.1.1 - Unauthenticated Remote File Inclusion

> Unauthenticated attackers can execute arbitrary PHP code via Remote File Inclusion if allow_url_include is enabled.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jun 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-62vj-fq75-3xhv

## What is CVE-2024-5577?

CVE-2024-5577 is a critical code injection vulnerability in mcnardelli Where I Was, Where I Will Be, published on 14 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Where I Was, Where I Will Be plugin for WordPress is vulnerable to Remote File Inclusion in version <= 1.1.1 via the WIW_HEADER parameter of the /system/include/include_user.php file. This makes it possible for unauthenticated attackers to include and execute arbitrary files hosted on external servers, 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. This requires allow_url_include to be set to true in order to exploit, which is not commonly enabled.

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

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


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

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

## Is CVE-2024-5577 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-5577 is a critical code injection vulnerability in mcnardelli Where I Was, Where I Will Be, published on 14 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-5577 in the wild and no public exploit code.

Affected product: mcnardelli Where I Was, Where I Will Be. 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-5577/ (Markdown: https://insights.sbomify.com/CVE-2024-5577/index.md)
```

## Sources

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

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