# CVE-2016-6174: applications/core/modules/front/system/content.php in Invision Power Services IPS Community Suite (aka Invision Power Board, IPB, or Power B


- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 12 Jul 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wpfq-fvm4-44jm

## What is CVE-2016-6174?

CVE-2016-6174 is a high-severity vulnerability in Php Php, published on 12 Jul 2016. 

### Official description

applications/core/modules/front/system/content.php in Invision Power Services IPS Community Suite (aka Invision Power Board, IPB, or Power Board) before 4.1.13, when used with PHP before 5.4.24 or 5.5.x before 5.5.8, allows remote attackers to execute arbitrary code via the content_class parameter.

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

It affects 2 products.


Products: Invisioncommunity Invision Power Board, Php Php.

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

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

## Is CVE-2016-6174 being exploited?

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

Public exploit code:

- IPS Community Suite 4.1.12.3 - PHP Code Injection (exploitdb)

## Other vulnerabilities in Php Php

- [CVE-2012-5692](https://insights.sbomify.com/CVE-2012-5692/): Other in n/a (critical 10.0)
- [CVE-2013-3725](https://insights.sbomify.com/CVE-2013-3725/): Auth bypass in n/a (critical 9.8)
- [CVE-2012-2226](https://insights.sbomify.com/CVE-2012-2226/): File upload in n/a (critical 9.8)
- [CVE-2017-8898](https://insights.sbomify.com/CVE-2017-8898/): Cross-site scripting in n/a (critical 9.8)
- [CVE-2014-4928](https://insights.sbomify.com/CVE-2014-4928/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6174 is a high-severity vulnerability in Php Php, published on 12 Jul 2016. 
Exploitation: There is no known exploitation of CVE-2016-6174 in the wild and no public exploit code.

Affected product: Php Php. 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-6174/ (Markdown: https://insights.sbomify.com/CVE-2016-6174/index.md)
```

## Sources

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

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