dbcve.org
WpdiscuzWordPress extension · Gvectors

CVE-2023-47775

HIGH · 8.8 CVSS v3.1 Published 2023-11-22
Fix available
A fix is available. Upgrade to 7.6.12 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 Comments — wpDiscuz plugin <= 7.6.11 versions.

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 the wpDiscuz (Comments — wpDiscuz) WordPress plugin versions 7.6.11 and below allows authenticated attackers to trick logged-in users into unknowingly executing unauthorized actions, such as manipulating comments or settings.

MitigationUpdate wpDiscuz to the patched version (if available) or implement CSRF tokens and validation checks on all state-changing forms and AJAX endpoints within the plugin.

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

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. Confirm wpDiscuz plugin is installed
    Access WordPress admin dashboard > Plugins, or check the /wp-content/plugins/wpdiscuz/ directory for the plugin files
    Affected if wpDiscuz plugin is present in the WordPress installation
  2. Identify installed wpDiscuz version
    In WordPress admin, go to Plugins > wpDiscuz and view the version number, or read the main plugin file (wpdiscuz.php) and locate the Version header
    Affected if Version is 7.6.11 or below (versions prior to 7.6.12 are in the affected range)
  3. Verify if plugin handles logged-in user actions
    Review the plugin for comment submission forms, settings modification forms, and AJAX endpoints that process state-changing requests from authenticated users
    Affected if The plugin processes comment submissions, ratings, or settings changes from logged-in WordPress users without CSRF protection
  4. Inspect forms for CSRF token validation
    Examine comment forms, settings forms, and AJAX handlers in wpdiscuz.php and related files for nonce verification or token validation calls (look for wp_verify_nonce, check_ajax_referer, or similar validation functions)
    Affected if State-changing forms and AJAX endpoints lack nonce/token validation checks, allowing forged requests from malicious sites

A WordPress site is affected if wpDiscuz version 7.6.11 or below is installed AND the plugin processes actions from logged-in users through forms or AJAX calls that do not validate CSRF tokens.

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 7.6.12 or later
Fixed in 7.6.12
Interim mitigation

Update wpDiscuz to the patched version (if available) or implement CSRF tokens and validation checks on all state-changing forms and AJAX endpoints within the plugin.

Recommended fix High confidence

wpDiscuz version 7.6.12

  1. Backup your WordPress database and files before updating
  2. Navigate to WordPress Admin Dashboard > Plugins
  3. Find the wpDiscuz plugin in the installed plugins list
  4. Click 'Update now' when version 7.6.12 is available, or manually upload version 7.6.12 if not showing
  5. Verify the plugin version is 7.6.12 after update completes
  6. Test that comments functionality works correctly

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

Fix this in Wpdiscuz Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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