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

> Remote attackers can obtain sensitive database credentials when database connectivity fails, exposing usernames and passwords to unauthorized users.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 1 Jun 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5wrp-5m5q-9w6x

## What is CVE-2014-9702?

CVE-2014-9702 is a high-severity vulnerability in n/a, published on 1 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

system/classes/DbPDO.php in Cmfive through 2015-03-15, when database connectivity malfunctions, allows remote attackers to obtain sensitive information (username and password) via any request, such as a password reset request.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: 2pisoftware Cmfive.

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

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

## Is CVE-2014-9702 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-9702 is a high-severity vulnerability in n/a, published on 1 Jun 2020. 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-9702 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-9702/ (Markdown: https://insights.sbomify.com/CVE-2014-9702/index.md)
```

## Sources

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

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