# CVE-2018-7664: An issue was discovered in ClipBucket before 4.0.0 Release 4902.


- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xxv9-6fj9-h72p

## What is CVE-2018-7664?

CVE-2018-7664 is a critical vulnerability in n/a, published on 5 Mar 2018. 

### Official description

An issue was discovered in ClipBucket before 4.0.0 Release 4902. Any OS commands can be injected via shell metacharacters in the file_name parameter to /api/file_uploader.php or /actions/file_downloader.php.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Clip-Bucket Clipbucket.

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

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

## Is CVE-2018-7664 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-10040](https://insights.sbomify.com/CVE-2013-10040/): ClipBucket <= 2.6 ofc_upload_image.php Arbitrary File Upload RCE (critical 10.0)
- [CVE-2018-7665](https://insights.sbomify.com/CVE-2018-7665/): File upload in n/a (critical 9.8)
- [CVE-2018-7666](https://insights.sbomify.com/CVE-2018-7666/): SQL injection in n/a (critical 9.8)
- [CVE-2012-5849](https://insights.sbomify.com/CVE-2012-5849/): SQL injection in n/a (high 7.5)
- [CVE-2015-2102](https://insights.sbomify.com/CVE-2015-2102/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-7664 is a critical vulnerability in n/a, published on 5 Mar 2018. 
Exploitation: There is no known exploitation of CVE-2018-7664 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-7664/ (Markdown: https://insights.sbomify.com/CVE-2018-7664/index.md)
```

## Sources

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

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