# CVE-2024-33329: Hardcoded credentials in n/a

> Attackers can bypass authentication using a hardcoded privileged ID to access internal pages and sensitive information in Lumisxp.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2024
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-v3rc-5q86-wwq8

## What is CVE-2024-33329?

CVE-2024-33329 is a high-severity vulnerability in n/a, published on 26 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A hardcoded privileged ID within Lumisxp v15.0.x to v16.1.x allows attackers to bypass authentication and access internal pages and other sensitive information.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2024-33329 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-33329 is a high-severity vulnerability in n/a, published on 26 Jun 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-33329 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-33329/ (Markdown: https://insights.sbomify.com/CVE-2024-33329/index.md)
```

## Sources

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

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