Skip to content
Fencer Intel
medium 4.3

CVE-2014-3849 json

The iMember360 plugin 3.8.012 through 3.9.001 for WordPress does not properly restrict access, which allows remote attackers to delete arbi…

published 12y ago modified 4mo ago also EUVD-2014-3786

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
6.0%
EPSS 6.0% chance of exploitation in 30 days, percentile 93%
public exploits
1
Exploit-DB

Summary

The iMember360 plugin 3.8.012 through 3.9.001 for WordPress does not properly restrict access, which allows remote attackers to delete arbitrary users via a request containing a user name in the Email parameter and the API key in the i4w_clearuser parameter.

Is CVE-2014-3849 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (EDB-33076)
  2. Published

Exploit prediction

5.97% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-33076 WordPress Plugin iMember360 3.8.012 < 3.9.001 - Multiple Vulnerabilities webapps, 2014-04-28
  • packetstormsecurity.com http://packetstormsecurity.com/files/126324/WordPress-iMember360is-3.9.001-XSS-Disclosure-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org http://seclists.org/fulldisclosure/2014/Apr/265 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.