# CVE-2024-46331: Open redirect in n/a

> Attackers can redirect users to arbitrary websites via a crafted URL in the admin login page of ModStartCMS.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2024
- **Updated:** 27 Sep 2024
- **Also known as:** GHSA-3gv3-rgph-2cgp

## What is CVE-2024-46331?

CVE-2024-46331 is a high-severity vulnerability in n/a, published on 27 Sep 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

ModStartCMS v8.8.0 was discovered to contain an open redirect vulnerability in the redirect parameter at /admin/login. This vulnerability allows attackers to redirect users to an arbitrary website via a crafted URL.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

It affects 1 product.


Products: Modstart Mostartcms.

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

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

## Is CVE-2024-46331 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-55824](https://insights.sbomify.com/CVE-2025-55824/): Command injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-46331 is a high-severity vulnerability in n/a, published on 27 Sep 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-46331 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-46331/ (Markdown: https://insights.sbomify.com/CVE-2024-46331/index.md)
```

## Sources

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

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