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

> Attackers can upload malicious PHP files disguised as documents to execute arbitrary code on the server.

- **Severity:** High 8.8 (`CVSS:3.0/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:** 28 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vp58-jf8j-hfgm

## What is CVE-2018-11514?

CVE-2018-11514 is a high-severity vulnerability in n/a, published on 28 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PHP Scripts Mall Naukri Clone Script through 3.0.3 allows Unrestricted Upload of a File with a Dangerous Type in edit_resume_det.php, as demonstrated by changing .docx to .php.

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

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

It affects 1 product.


Products: Naukri Clone Script Project Naukri Clone Script.

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

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

## Is CVE-2018-11514 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-15185](https://insights.sbomify.com/CVE-2018-15185/): Denial of service in n/a (medium 6.5)
- [CVE-2018-15184](https://insights.sbomify.com/CVE-2018-15184/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2018-6795](https://insights.sbomify.com/CVE-2018-6795/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-11514 is a high-severity vulnerability in n/a, published on 28 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-11514 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-11514/ (Markdown: https://insights.sbomify.com/CVE-2018-11514/index.md)
```

## Sources

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

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