dbcve.org
Wpforo ForumWordPress extension · Gvectors

CVE-2022-40200

HIGH · 8.8 CVSS v3.1 Published 2022-11-17
Fix available
A fix is available. Upgrade to after 2.0.9 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Auth. (subscriber+) Arbitrary File Upload vulnerability in wpForo Forum plugin <= 2.0.9 on 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 · moderate confidence

Authenticated users with subscriber-level access or higher can upload arbitrary files to the server through the wpForo Forum plugin versions 2.0.9 and earlier, potentially allowing remote code execution via malicious file uploads.

MitigationUpdate wpForo Forum plugin to version 2.1.0 or higher; as an interim measure, disable PHP execution in upload directories and restrict file type uploads.

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.9

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Verify wpForo Forum plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'wpForo Forum' or 'wpForo' in the plugin list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'wpforo' or similar.
    Affected if The wpForo Forum plugin is present in the WordPress installation
  2. Determine installed wpForo version
    In WordPress admin, go to Plugins > Installed Plugins and find wpForo Forum. The version number is displayed below the plugin name. Alternatively, check the main plugin file (e.g., wpforo.php) for the 'Version' header comment.
    Affected if The installed version is 2.0.9 or any earlier version (e.g., 2.0.8, 2.0.7, etc.)
  3. Confirm subscriber-level access exists
    Navigate to WordPress admin > Users > Roles or Users > All Users to review existing user accounts and their assigned roles. Check if any users have the 'Subscriber' role or any role with equivalent or lower privileges.
    Affected if At least one user account with Subscriber-level access or higher exists on the site
  4. Verify forum upload functionality is active
    Visit the active wpForo forum pages on the site (typically at /community/ or /forums/) and check if the upload attachment feature is available. This may appear on forum topics, posts, or user profile areas.
    Affected if The forum upload/attachment feature is enabled and accessible to registered users

A site is affected if wpForo Forum plugin version 2.0.9 or earlier is installed, subscriber-level users exist, and the forum upload feature is active, allowing authenticated users to potentially upload malicious files.

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.9
Interim mitigation

Update wpForo Forum plugin to version 2.1.0 or higher; as an interim measure, disable PHP execution in upload directories and restrict file type uploads.

Recommended fix Moderate confidence

wpForo Forum version higher than 2.0.9 (check WordPress plugin repository for latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the wpForo Forum plugin
  4. Check the current version to confirm it is 2.0.9 or lower
  5. If an update is available, click 'Update Now' to upgrade the plugin
  6. After updating, verify the new version number in the plugins list
  7. Ensure the 'Allow File Uploads' setting in wpForo Forum settings is properly configured according to your security requirements
Caveat Review plugin settings after upgrade as default configurations may have changed

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

Fix this in Wpforo Forum Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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