# CVE-2025-4634: Local File Inclusion

> An authenticated administrator can exploit local file inclusion to read arbitrary files from the server filesystem.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2025
- **Updated:** 30 May 2025
- **Also known as:** GHSA-67x9-8jxx-85f8

## What is CVE-2025-4634?

CVE-2025-4634 is a medium-severity path traversal vulnerability in JCT Airpointer, published on 30 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The web portal on airpointer 2.4.107-2 was vulnerable local file inclusion. A malicious user with administrative privileges in the web portal would be able to manipulate requests to view files on the filesystem

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

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


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

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

## Is CVE-2025-4634 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4634 is a medium-severity path traversal vulnerability in JCT Airpointer, published on 30 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4634 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-4634/ (Markdown: https://insights.sbomify.com/CVE-2025-4634/index.md)
```

## Sources

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

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