# CVE-2024-38295: Code injection in n/a

> Remote attackers can execute arbitrary code on ALCASAR captive portal servers via the still_connected.php script.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2024
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-mj6c-grgr-xq75

## What is CVE-2024-38295?

CVE-2024-38295 is a high-severity code injection vulnerability in n/a, published on 13 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ALCASAR before 3.6.1 allows still_connected.php remote code execution.

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

It affects 1 product.


Products: Alcasar Alcasar.

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

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

## Is CVE-2024-38295 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-38293](https://insights.sbomify.com/CVE-2024-38293/): ALCASAR before 3.6.1 allows CSRF and remote code execution in activity.php. (critical 9.6)
- [CVE-2024-38294](https://insights.sbomify.com/CVE-2024-38294/): ALCASAR before 3.6.1 allows email_registration_back.php remote code execution. (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38295 is a high-severity code injection vulnerability in n/a, published on 13 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-38295 in the wild and no public exploit code.

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-38295/ (Markdown: https://insights.sbomify.com/CVE-2024-38295/index.md)
```

## Sources

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

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