# CVE-2014-8081: Code injection in n/a

> Remote attackers can execute arbitrary PHP code via a parameter in TestLink, requiring low privileges.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 31 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r7cx-cqwc-hf28

## What is CVE-2014-8081?

CVE-2014-8081 is a high-severity code injection vulnerability in n/a, published on 31 Oct 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

lib/execute/execSetResults.php in TestLink before 1.9.13 allows remote attackers to conduct PHP object injection attacks and execute arbitrary PHP code via the filter_result_result parameter.

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

## Which versions are affected by CVE-2014-8081?

It affects 1 product.


Products: Testlink Testlink.

## How do I fix CVE-2014-8081?

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

## Is CVE-2014-8081 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6006](https://insights.sbomify.com/CVE-2007-6006/): Missing authorization in n/a (critical 10.0)
- [CVE-2020-12274](https://insights.sbomify.com/CVE-2020-12274/): Open redirect in n/a (critical 9.8)
- [CVE-2020-8637](https://insights.sbomify.com/CVE-2020-8637/): SQL injection in n/a (critical 9.8)
- [CVE-2020-8638](https://insights.sbomify.com/CVE-2020-8638/): SQL injection in n/a (critical 9.8)
- [CVE-2015-7390](https://insights.sbomify.com/CVE-2015-7390/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-8081 and fix it if it is affected.

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

## Sources

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

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