How severe is CVE-2018-16613?

CVE-2018-16613 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2018-16613 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (84th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2018-16613?

CVE-2018-16613 affects Gvectors Wpforo Forum. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2018-16613?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2018-16613 published?

CVE-2018-16613 was published on 2019-06-19 and last updated on 2026-06-17.

CVE-2018-16613

CVE-2018-16613 is a critical-severity vulnerability in Gvectors Wpforo Forum with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v2: 7.5
EPSS exploit prediction: 3% (84th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Gvectors Wpforo Forum
Published: 2019-06-19
Last modified: 2026-06-17

Description

An issue was discovered in the update function in the wpForo Forum plugin before 1.5.2 for WordPress. A registered forum is able to escalate privilege to the forum administrator without any form of user interaction.

Frequently asked questions

What is CVE-2018-16613?: An issue was discovered in the update function in the wpForo Forum plugin before 1.5.2 for WordPress. A registered forum is able to escalate privilege to the forum administrator without any form of user interaction.
How severe is CVE-2018-16613?: CVE-2018-16613 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2018-16613 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (84th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-16613?: CVE-2018-16613 affects Gvectors Wpforo Forum. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-16613?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2018-16613 published?: CVE-2018-16613 was published on 2019-06-19 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:gvectors:wpforo_forum:*:*:*:*:*:wordpress:*:*

More vulnerabilities in Gvectors Wpforo Forum

CVE-2024-3200 — Critical (CVSS 9.9): The wpForo Forum plugin for WordPress is vulnerable to SQL Injection via the 'slug' attribute of the 'wpforo' shortcode…
CVE-2022-40200 — Critical (CVSS 9.9): Auth. (subscriber+) Arbitrary File Upload vulnerability in wpForo Forum plugin <= 2.0.9 on WordPress.
CVE-2023-2249 — High (CVSS 8.8): The wpForo Forum plugin for WordPress is vulnerable to Local File Include, Server-Side Request Forgery, and PHAR…
CVE-2022-38144 — High (CVSS 8.8): Cross-Site Request Forgery (CSRF) vulnerability in gVectors Team wpForo Forum plugin <= 2.0.5 at WordPress.
CVE-2026-28562 — High (CVSS 8.2): wpForo 2.4.14 contains an unauthenticated SQL injection vulnerability in Topics::get_topics() where the ORDER BY clause…
CVE-2024-43289 — High (CVSS 7.5): Exposure of Sensitive Information to an Unauthorized Actor vulnerability in gVectors Team wpForo Forum.This issue…

All CVEs affecting Gvectors Wpforo Forum →