# CVE-2024-5514: MinMax CMS - Hidden Functionality

> Attackers can use a hidden administrator account with a fixed password to bypass access controls and log in without detection.

- **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:** 30 May 2024
- **Updated:** 25 Nov 2024

## What is CVE-2024-5514?

CVE-2024-5514 is a critical vulnerability in MinMax CMS, published on 30 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MinMax CMS from MinMax Digital Technology contains a hidden administrator account with a fixed password that cannot be removed or disabled from the management interface. Remote attackers who obtain this account can bypass IP access control restrictions and log in to the backend system without being recorded in the system logs.

Weakness: CWE-912 (Hidden Functionality), CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2024-5514 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-5514 is a critical vulnerability in MinMax CMS, published on 30 May 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-5514 in the wild and no public exploit code.

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

## Sources

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

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