The users-ultra plugin before 1.5.64 for WordPress has SQL Injection via an ajax action.

published 2019-09-20 7y ago modified 2026-06-17 4mo ago also EUVD-2015-9235

cvss: 8.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.7%; EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits: 0; none known

Patch / fix

fixed in 1

usersultra users_ultra_membership 1.5.64

Is CVE-2015-9395 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

Exploit prediction

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

CVSS scores

assigned by	version	score	vector
NVD	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	6.5	AV:N/AC:L/Au:S/C:P/I:P/A:P

Classification

Weakness

CWE-89 Improper Neutralization of Special Elements used in an SQL Command

Technology feeds

WordPress rss critical rss

References

wordpress.org /plugins/users-ultra/#developers
product, release-notes
wpvulndb.com /vulnerabilities/8349/
third-party-advisory
seclists.org /bugtraq/2015/Dec/12
mailing-list, third-party-advisory

Sources

CVE List CVE-2015-9395
NVD CVE-2015-9395

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.