The wpForo plugin through 2018-02-05 for WordPress has SQL Injection via a search with the /forum/ wpfo parameter.

published 2018-05-28 8y ago modified 2026-06-17 4mo ago also EUVD-2018-3544

cvss: 9.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.6%; EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits: 0; none known

Patch / fix

fixed in 1

gvectors wpforo 1.4.5

Is CVE-2018-11515 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.59% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

wpvulndb.com https://wpvulndb.com/vulnerabilities/9089 referenced PoC, tagged "exploit" by a source, unverified
github.com https://github.com/DediData/wpforo/issues/1 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness

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

Technology feeds

WordPress rss critical rss

References

wpvulndb.com /vulnerabilities/9089
exploit, third-party-advisory
github.com /DediData/wpforo/issues/1
exploit, issue-tracking, third-party-advisory

Sources

CVE List CVE-2018-11515
NVD CVE-2018-11515

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.