# CVE-2024-41617: Missing authorization in n/a

> An unauthenticated attacker can upload arbitrary files and execute code due to a missing exit statement after a redirect in the login check.

- **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:** 24 Oct 2024
- **Updated:** 29 Oct 2024
- **Also known as:** GHSA-643q-778f-w3wx

## What is CVE-2024-41617?

CVE-2024-41617 is a critical missing authorization vulnerability in n/a, published on 24 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Money Manager EX WebApp (web-money-manager-ex) 1.2.2 is vulnerable to Incorrect Access Control. The `redirect_if_not_loggedin` function in `functions_security.php` fails to terminate script execution after redirecting unauthenticated users. This flaw allows an unauthenticated attacker to upload arbitrary files, potentially leading to Remote Code Execution.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2024-41617 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41617 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41617 is a critical missing authorization vulnerability in n/a, published on 24 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41617 exists.

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

## Sources

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

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