dbcve.org
Wpforo ForumWordPress extension · Gvectors

CVE-2022-40632

MEDIUM · 5.4 CVSS v3.1 Published 2022-11-08
Fix available
A fix is available. Upgrade to after 2.0.5 or later.
See remediation →
61/100
Remediation priority · Elevated
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 on WordPress leading to topic deletion.

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 <= 2.0.5 on WordPress allows attackers to delete forum topics by tricking authenticated users into unknowingly submitting malicious requests.

MitigationImplement anti-CSRF tokens (nonces) on all topic deletion forms and validate nonce parameters on the server-side before processing deletion requests.

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
None
Integrity
Low
Availability
Low

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

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. Verify wpForo Forum plugin is installed
    Log in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'wpForo Forum' or 'wpForo' in the plugin list.
    Affected if The plugin is not present in the WordPress installation
  2. Check installed plugin version
    In the Plugins list, locate wpForo Forum and view the version number displayed under the plugin name. Alternatively, check the main plugin file (typically /wp-content/plugins/wpforo/wpforo.php) for the 'Version' header in the plugin comment block.
    Affected if The installed version is 2.0.5 or lower (any version <= 2.0.5)
  3. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that wpForo Forum shows as 'Active' rather than 'Inactive'.
    Affected if The plugin is active and topic deletion functionality is available to authenticated users
  4. Identify topic deletion endpoint
    Access the wpForo forum on the frontend as an authenticated user with topic deletion permissions. Locate a forum topic and identify the deletion form or action (typically involves a delete link or button).
    Affected if Topic deletion feature is accessible to logged-in users
  5. Inspect deletion form for anti-CSRF protection
    View the HTML source of the topic deletion form (right-click > View Page Source). Look for a hidden input field named 'wpfnonce' or similar nonce token, or check if the form submits to an endpoint that validates a nonce parameter.
    Affected if The deletion form lacks a nonce token field AND the server does not validate any CSRF token before processing the deletion request

A user is affected if wpForo Forum plugin version 2.0.5 or lower is installed and active, and the topic deletion functionality lacks proper CSRF token validation.

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

Implement anti-CSRF tokens (nonces) on all topic deletion forms and validate nonce parameters on the server-side before processing deletion requests.

Recommended fix Moderate confidence

wpForo Forum 2.0.6 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the wpForo Forum plugin
  4. Check the current version installed (should be <= 2.0.5)
  5. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org
  6. Update to the latest available version which contains the security fix
  7. Verify the update completed successfully

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-40632 — 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-40632 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