# CVE-2025-4633: Default Credentials

> Unauthenticated attackers can log in to the Airpointer web portal using default credentials, gaining unauthorized access.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 30 May 2025
- **Updated:** 30 May 2025
- **Also known as:** GHSA-gx9w-mmx8-h596

## What is CVE-2025-4633?

CVE-2025-4633 is a medium-severity vulnerability in JCT Airpointer, published on 30 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Default credentials were present in the web portal for Airpointer 2.4.107-2, allowing an unauthenticated malicious actor to log in via the web portal

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

## Which versions are affected by CVE-2025-4633?


## How do I fix CVE-2025-4633?

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

## Is CVE-2025-4633 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4633 and fix it if it is affected.

What it is: CVE-2025-4633 is a medium-severity vulnerability in JCT Airpointer, published on 30 May 2025. 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-2025-4633 in the wild and no public exploit code.

Affected product: JCT Airpointer. 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-2025-4633/ (Markdown: https://insights.sbomify.com/CVE-2025-4633/index.md)
```

## Sources

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

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