# CVE-2024-9275: jeanmarc77 123solar admin_invt2.php file inclusion

> Remote attackers can exploit a file inclusion vulnerability in 123solar to execute arbitrary code or read sensitive files.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **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:** 27 Sep 2024
- **Updated:** 27 Sep 2024
- **Also known as:** GHSA-p6qp-r9qf-v2m7

## What is CVE-2024-9275?

CVE-2024-9275 is a medium-severity path traversal vulnerability in jeanmarc77 123solar, published on 27 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in jeanmarc77 123solar up to 1.8.4.5. It has been rated as critical. This issue affects some unknown processing of the file /admin/admin_invt2.php. The manipulation of the argument PROTOCOLx leads to file inclusion. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2024-9275 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-9275 is a medium-severity path traversal vulnerability in jeanmarc77 123solar, published on 27 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-9275 exists.

Affected product: jeanmarc77 123solar. 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-9275/ (Markdown: https://insights.sbomify.com/CVE-2024-9275/index.md)
```

## Sources

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

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