# CVE-2016-4895: Code injection in n/a

> Remote authenticated attackers can execute arbitrary code in SetsucoCMS via unspecified vectors, posing a critical risk to system integrity.

- **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:** 12 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-285q-4mr9-9qmp

## What is CVE-2016-4895?

CVE-2016-4895 is a high-severity code injection vulnerability in n/a, published on 12 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SetsucoCMS all versions allows remote authenticated attackers to conduct code injection attacks via unspecified vectors.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2016-4895?

It affects 1 product.


Products: Setucocms Project Setucocms.

## How do I fix CVE-2016-4895?

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

## Is CVE-2016-4895 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-4891](https://insights.sbomify.com/CVE-2016-4891/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2016-4893](https://insights.sbomify.com/CVE-2016-4893/): SQL injection in n/a (high 8.8)
- [CVE-2016-4896](https://insights.sbomify.com/CVE-2016-4896/): Missing authorization in n/a (medium 6.5)
- [CVE-2016-4892](https://insights.sbomify.com/CVE-2016-4892/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2016-4894](https://insights.sbomify.com/CVE-2016-4894/): Denial of service in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-4895 and fix it if it is affected.

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

## Sources

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

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