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

> Remote attackers can obtain database credentials via the i4w_dbinfo parameter in the iMember360 WordPress plugin due to improper access restrictions.

- **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:** 23 May 2014
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qgmq-8wm8-jj4m

## What is CVE-2014-3848?

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

### Official description

The iMember360 plugin before 3.9.001 for WordPress does not properly restrict access, which allows remote attackers to obtain database credentials via the i4w_dbinfo parameter.

Weakness: CWE-264

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

It affects 1 product.


Products: Imember360 Imember360.

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

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

## Is CVE-2014-3848 being exploited?

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

Public exploit code:

- WordPress Plugin iMember360 3.8.012 < 3.9.001 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-8948](https://insights.sbomify.com/CVE-2014-8948/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2014-8949](https://insights.sbomify.com/CVE-2014-8949/): Command injection in n/a (medium 6.0)
- [CVE-2014-3849](https://insights.sbomify.com/CVE-2014-3849/): Missing authorization in n/a (medium 4.3)
- [CVE-2014-3842](https://insights.sbomify.com/CVE-2014-3842/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-3848 is a medium-severity vulnerability in n/a, published on 23 May 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-3848 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-3848/ (Markdown: https://insights.sbomify.com/CVE-2014-3848/index.md)
```

## Sources

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

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