dbcve.org
WpdiscuzWordPress extension · Gvectors

CVE-2020-24186

CRITICAL · 10.0 CVSS v3.1 Published 2020-08-24
Fix available
A fix is available. Upgrade to after 7.0.4 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Public exploit Remotely reachable No privileges 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
A Remote Code Execution vulnerability exists in the gVectors wpDiscuz plugin 7.0 through 7.0.4 for WordPress, which allows unauthenticated users to upload any type of file, including PHP files via the wmuUploadFiles AJAX action.

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

The wpDiscuz plugin versions 7.0 through 7.0.4 for WordPress contains an insecure file upload vulnerability in the wmuUploadFiles AJAX action, allowing unauthenticated attackers to upload arbitrary files including malicious PHP scripts, leading to remote code execution on the affected WordPress installation.

MitigationUpdate wpDiscuz to version 7.0.5 or later immediately. As a temporary measure, disable the plugin or block access to the wmuUploadFiles AJAX endpoint via web server configuration until the update can be applied.

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
WpdiscuzWordPress extension
Affected:>= 7.0, <= 7.0.4

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
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 wpDiscuz plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the wpdiscuz folder, or view the installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if The wpdiscuz folder exists in the plugins directory or the plugin appears in WordPress admin plugins list
  2. Determine installed wpDiscuz version
    Check the main plugin file (wp-content/plugins/wpdiscuz/class.WpdiscuzCore.php) for the version constant, or look in the plugin header of any wpdiscuz PHP file. In WordPress admin, click on the plugin to see its version number
    Affected if The version number is 7.0, 7.0.1, 7.0.2, 7.0.3, or 7.0.4 (any version >= 7.0 and <= 7.0.4)
  3. Confirm wmuUploadFiles AJAX endpoint exists and is accessible
    Check if the file wp-content/plugins/wpdiscuz/utils/ajax/wmuAjax.php exists, or attempt a HEAD request to the AJAX endpoint /wp-admin/admin-ajax.php?action=wmuUploadFiles (note: actual endpoint may vary)
    Affected if The wmuAjax.php file exists in the plugin directory, indicating the vulnerable upload functionality is present
  4. Check if comments are enabled on the site
    Visit the WordPress site and attempt to view or post a comment. Check WordPress admin under Settings > Discussion if comment posting is allowed
    Affected if Comments are enabled and the wpDiscuz comment system is active, as the vulnerability requires the comment upload feature to be functional

The site is affected if wpDiscuz version 7.0-7.0.4 is installed AND the comment upload feature is active, exposing the wmuUploadFiles AJAX endpoint to unauthenticated file uploads.

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 7.0.4
Interim mitigation

Update wpDiscuz to version 7.0.5 or later immediately. As a temporary measure, disable the plugin or block access to the wmuUploadFiles AJAX endpoint via web server configuration until the update can be applied.

Recommended fix Moderate confidence

wpDiscuz 7.0.5 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find wpDiscuz in the plugin list
  4. Click 'Update now' if an update is available, or manually update to version 7.0.5 or later
  5. Verify the update was successful by checking the plugin version

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

Fix this in Wpdiscuz Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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