# CVE-2014-8874: Information disclosure in n/a

> Remote attackers can obtain sensitive questionnaire data by guessing predictable form names in the ke_questionnaire TYPO3 extension.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f4wj-qq69-7p3q

## What is CVE-2014-8874?

CVE-2014-8874 is a medium-severity vulnerability in n/a, published on 2 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ke_questionnaire extension 2.5.2 and earlier for TYPO3 uses predictable names for the questionnaire answer forms, which makes it easier for remote attackers to obtain sensitive information via a direct request.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Kennziffer Ke Questionnaire.

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

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

## Is CVE-2014-8874 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-8874 is a medium-severity vulnerability in n/a, published on 2 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-8874 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-8874/ (Markdown: https://insights.sbomify.com/CVE-2014-8874/index.md)
```

## Sources

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

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