# CVE-2015-6967: File upload in n/a

> Remote administrators can execute arbitrary code by uploading malicious files to the My Image plugin in Nibbleblog.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2015
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-jc49-pxch-59wj

## What is CVE-2015-6967?

CVE-2015-6967 is a medium-severity vulnerability in n/a, published on 16 Sep 2015. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in the My Image plugin in Nibbleblog before 4.0.5 allows remote administrators to execute arbitrary code by uploading a file with an executable extension, then accessing it via a direct request to the file in content/private/plugins/my_image/image.php.

## Which versions are affected by CVE-2015-6967?

It affects 1 product.


Products: Nibbleblog Nibbleblog.

## How do I fix CVE-2015-6967?

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

## Is CVE-2015-6967 being exploited?

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

Public exploit code:

- Nibbleblog 4.0.3 - Arbitrary File Upload (CVE-2015-6967) (github_poc): https://github.com/dix0nym/CVE-2015-6967
- Nibbleblog File Upload Vulnerability (metasploit)
- Nibbleblog 4.0.3 - Arbitrary File Upload (Metasploit) (exploitdb)
- An exploit for the Nibbles manager version 4.0.3. This exploit allows RCE to be performed. (github_poc): https://github.com/FredBrave/CVE-2015-6967
- In this repository you will find the technical report of Nibbles, the exploit to abuse the CVE-2015-6967 and an autopwn tool in case you want to resolve the machine in HackTheBox (github_poc): https://github.com/3mpir3Albert/HTB_Nibbles
- https://github.com/cuerv0x/CVE-2015-6967 (github_poc): https://github.com/cuerv0x/CVE-2015-6967

## Other vulnerabilities in n/a

- [CVE-2019-7719](https://insights.sbomify.com/CVE-2019-7719/): Code injection in n/a (critical 9.8)
- [CVE-2020-23356](https://insights.sbomify.com/CVE-2020-23356/): Auth bypass in n/a (high 7.5)
- [CVE-2018-16604](https://insights.sbomify.com/CVE-2018-16604/): Code injection in n/a (high 7.2)
- [CVE-2015-6966](https://insights.sbomify.com/CVE-2015-6966/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2018-6470](https://insights.sbomify.com/CVE-2018-6470/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-6967 and fix it if it is affected.

What it is: CVE-2015-6967 is a medium-severity vulnerability in n/a, published on 16 Sep 2015. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-6967 exists.

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

## Sources

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

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