dbcve.org
Wpforo ForumWordPress extension · Gvectors

CVE-2022-38144

HIGH · 8.8 CVSS v3.1 Published 2022-09-09
Fix available
A fix is available. Upgrade to after 2.0.5 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability in gVectors Team wpForo Forum plugin <= 2.0.5 at WordPress.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross-Site Request Forgery (CSRF) vulnerability in wpForo Forum plugin versions 2.0.5 and earlier allows attackers to perform unauthorized actions on behalf of authenticated users by tricking them into visiting malicious pages or clicking links. The plugin fails to properly validate anti-CSRF tokens (nonces) on state-changing operations, enabling attackers to execute forum actions like modifying settings, posts, or user permissions.

MitigationUpdate wpForo Forum plugin to version 2.0.6 or later which includes nonce validation. If immediate update is not possible, ensure WordPress admin sessions are not left active while browsing untrusted sites, and consider implementing additional server-side CSRF protections at the web server level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wpforo ForumWordPress extension
Affected:<= 2.0.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify wpForo Forum plugin installation
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and locate wpForo Forum in the list. Note its version number displayed beneath the plugin name.
    Affected if wpForo Forum plugin is not found or not installed, the vulnerability does not apply
  2. Compare installed version to affected range
    Compare the installed version number against the affected range: versions 2.0.5 and earlier are vulnerable. The vulnerable versions are any release <= 2.0.5.
    Affected if Installed version is 2.0.5 or any earlier version number (e.g., 2.0.4, 2.0.3, 1.x.x)
  3. Confirm plugin is active on the site
    In the WordPress Plugins list, verify that wpForo Forum shows as 'Active' rather than 'Inactive' or 'Must-Use'. Only active installations process the vulnerable state-changing operations.
    Affected if Plugin is active and the forum functionality is accessible to users or administrators
  4. Determine if site accepts state-changing forum actions
    Check whether the forum allows authenticated users to perform actions such as creating or editing posts, modifying forum settings, or changing user permissions. These are the operations lacking proper nonce validation in affected versions.
    Affected if Forum functionality is enabled and users can perform modifications to posts, settings, or user permissions

If wpForo Forum plugin version 2.0.5 or earlier is installed and active on the WordPress site, the environment is affected by this CSRF vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.0.5
Interim mitigation

Update wpForo Forum plugin to version 2.0.6 or later which includes nonce validation. If immediate update is not possible, ensure WordPress admin sessions are not left active while browsing untrusted sites, and consider implementing additional server-side CSRF protections at the web server level.

Recommended fix Moderate confidence

Update to the latest version of wpForo Forum plugin available on wordpress.org (version 2.0.6 or higher, as the vulnerability was patched in version 2.0.6)

  1. Check the current version of the wpForo Forum plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. If the installed version is 2.0.5 or lower, update the plugin to the latest available version from the official WordPress plugin repository
  4. After updating, verify the plugin version in the admin dashboard to confirm the update was successful
  5. Test critical forum functionality (posting, replying, user registration) to ensure the update did not break existing functionality
Caveat Minor version updates typically do not introduce breaking changes, but always backup your site before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wpforo Forum Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38144 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38144 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data