# CVE-2018-19457: File upload in n/a

> Attackers can upload arbitrary PHP files to execute remote commands on the server hosting the Logicspice FAQ Script.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6f5p-7f6x-mhq9

## What is CVE-2018-19457?

CVE-2018-19457 is a high-severity vulnerability in n/a, published on 22 Nov 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Logicspice FAQ Script 2.9.7 allows uploading arbitrary files, which leads to remote command execution via admin/faqs/faqimages with a .php file.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2018-19457?

It affects 1 product.


Products: Logicspice Faq Script.

## How do I fix CVE-2018-19457?

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

## Is CVE-2018-19457 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-19457 and fix it if it is affected.

What it is: CVE-2018-19457 is a high-severity vulnerability in n/a, published on 22 Nov 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-19457 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-2018-19457/ (Markdown: https://insights.sbomify.com/CVE-2018-19457/index.md)
```

## Sources

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

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